http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47762
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-04-16
23:44:19 UTC ---
> See if, by chance, libstdc++/52604 did the "miracle". I would like that ;)
Yep! At revision 186396, I get for
RUNTESTFLAGS="conformance.exp=deallocate_global_thread* ..."
Running target unix/-m32
FAIL: ext/mt_allocator/deallocate_global_thread-1.cc execution test
FAIL: ext/mt_allocator/deallocate_global_thread-3.cc execution test
=== libstdc++ Summary for unix/-m32 ===
# of expected passes 2
# of unexpected failures 2
Running target unix/-m64
FAIL: ext/mt_allocator/deallocate_global_thread-1.cc execution test
FAIL: ext/mt_allocator/deallocate_global_thread-3.cc execution test
=== libstdc++ Summary for unix/-m64 ===
# of expected passes 2
# of unexpected failures 2
=== libstdc++ Summary ===
# of expected passes 4
# of unexpected failures 4
With the change in revision 186414, I get
=== libstdc++ Summary for unix/-m32 ===
# of expected passes 4
=== libstdc++ Summary for unix/-m64 ===
# of expected passes 4
=== libstdc++ Summary ===
# of expected passes 8
