[Bug sanitizer/55309] gcc's address-sanitizer 66% slower than clang's

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55309

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-02-05 09:56:17 UTC ---
"464.h264ref with gcc loops forever, I did not investigate why."
is PR53073 , you can use -fno-aggressive-loop-optimizations to workaround the
invalid code in SPEC.
As for runtime performance of gcc -fsanitize=address code, it would be
interesting to try also with Dodji's patchset, how that improves things.

And, for compile time, you want to be testing with --enable-checking=release
built gcc, that is what people will actually use if they aren't developing gcc.