http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55518
--- Comment #6 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-11-28 20:18:00 UTC --- Jakub, I've reposted the current results on x86_64-apple-darwin12 for... make -k check RUNTESTFLAGS="--target_board=unix'{-fsanitize=address}'" with manual adjustments to the build so that libasan is always found. http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg02388.html Ignore the objc and obj-c++ issues which are related to pre-existing linker problems in those libs. There are a huge number of failures in the g++ and libstdc++-v3 testsuite triggered by the use of fsanitize=address that merit examination. The g++ and libstdc++-v3 failures almost all appear to be either involving ASAN:SIGSEGV (some with many instances with a single failure) or segfaults with no output from libasan as all.