Encouraging preliminary results implementing memcpy in D

Mike Franklin slavo5150 at yahoo.com
Wed Jun 13 12:49:28 UTC 2018


On Wednesday, 13 June 2018 at 12:45:26 UTC, Fra Mecca wrote:
> I get this on Linux 4.16.3-gentoo, AMD FX(tm)-6100 Six-Core 
> Processor, 8GiB ram,
>
> using ldc2 -O3L:
> size memcpyC memcpyD
> 1 5 0
> 2 0 0
> 4 0 0
> 8 0 0
> 16 1519 0
> 32 1833 0
> 64 3816 0
> 128 7543 0
> 256 146500 0
> 512 194818 0
> 1024 329593 846142
> 2048 714945 1117132
> 4096 1596170 1803621
> 8192 5899818 6110026
> 16384 12338384 14141850
> 32768 24971315 26771484
> 65536 49806637 63260128
>
> size memcpyC memcpyD
> 1 0 0
> 1 0 0
> 1 0 0
> 2 0 0
> 2 0 0
> 4 0 0
> 4 0 0
> 8 0 0
> 8 0 0
> 4 0 0
> 8 0 0
> core.exception.AssertError at memcpyd.d(9): Assertion failure
> ----------------
> ??:? _d_assert [0xcaf056d5]
> ??:? [0xa015e7fe]
> ??:? [0xa0158cb0]
> ??:? void rt.dmain2._d_run_main(int, char**, extern (C) int 
> function(char[][])*).runAll() [0xcaf29daf]
> ??:? _d_run_main [0xcaf29c7b]
> ??:? __libc_start_main [0xca160eeb]
> ??:? [0xa0158b29]

Yes, optimizations are throwing code away.  I'm working on it.

Mike


More information about the Digitalmars-d-announce mailing list