This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[v3] fix x86_64 specific parallel fails

From: "Benjamin Kosnik" <bkoz at redhat dot com>
To: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
Date: Thu, 27 Sep 2007 13:04:43 -0500
Subject: [v3] fix x86_64 specific parallel fails

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

Attachment: p.20070927-1
Description: Binary data

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]