[v3] fix x86_64 specific parallel fails

Benjamin Kosnik bkoz@redhat.com
Thu Sep 27 18:45:00 GMT 2007


Johannes noticed these 7 extra fails on x86_64 in parallel mode:

FAIL: 21_strings/basic_string/cons/char/1.cc // __gnu_test::set_memory_limits();
FAIL: 21_strings/basic_string/cons/wchar_t/1.cc //
__gnu_test::set_memory_limits();
FAIL: 21_strings/basic_string/insert/char/1.cc  //
__gnu_test::set_memory_limits();
FAIL: 21_strings/basic_string/insert/wchar_t/1.cc //
__gnu_test::set_memory_limits();
FAIL: 22_locale/locale/cons/12438.cc  //  __gnu_test::set_memory_limits(10.0);
FAIL: 27_io/ios_base/storage/1.cc  // __gnu_test::set_memory_limits();
FAIL: 27_io/ios_base/storage/2.cc // __gnu_test::set_memory_limits();

which all had these testsuite.log signatures:

terminate called after throwing an instance of 'St9bad_alloc'
  what():  std::bad_alloc

The fix is to adjust for libgomp in set_memory_limits.

-benjamin

tested x86/linux + parallel
tested x86_64/linux + parallel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p.20070927-1
Type: application/octet-stream
Size: 1561 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20070927/533c67fc/attachment.obj>


More information about the Gcc-patches mailing list