https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100769
--- Comment #3 from Iain Buclaw <ibuclaw at gdcproject dot org> --- (In reply to Witold Baryluk from comment #2) > Hmm. It appears that using `import core.stdc.string : memcmp;` actually > resolves the problem. It looks like my manually declaration of memcmp for > some reason disabled optimisations for memcmp. Yes, for protective reasons, only extern(C) symbols in `core.stdc` are considered as possible candidates for mapping to GCC built-ins.
