https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58321
--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Eric Gallager from comment #6) > (In reply to Dominique d'Humieres from comment #3) > > Still present at r220301 (see > > https://gcc.gnu.org/ml/gcc-testresults/2015-01/msg03581.html). Does the > > patch in comment 2 makes sense or is there a better fix? > > cc-ing FX from that I have a local patch for this too, which I'm intending to apply as time permits. The main difference is explaining the reason that Darwin is different - and simplifying the condition. /* { dg-do compile } */ /* { dg-options "-O2 -march=atom -mmemcpy-strategy=vector_loop:2000:align,libcall:-1:align" } */ -/* { dg-final { scan-assembler-times "memcpy" 2 } } */ +/* one hit comes from the .file directive. */ +/* { dg-final { scan-assembler-times "memcpy" 2 { target { ! *-*-darwin* } } } } */ +/* but not on Darwin. */ +/* { dg-final { scan-assembler-times "_memcpy" 1 { target *-*-darwin* } } } */ char a[2048]; char b[2048];
