This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/29639] New: FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Oct 2006 23:54:52 -0000
- Subject: [Bug target/29639] New: FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Between 2006-10-28 and 2006-10-29 a regression appeared on at least some
targets:
http://gcc.gnu.org/ml/gcc-testresults/2006-10/msg01448.html
http://gcc.gnu.org/ml/gcc-testresults/2006-10/msg01450.html
On i686-pc-linux-gnu, I'm seeing it only at -O1 or above, and goes like this:
#0 parse_lsda_header (context=0xbf80ae54, p=0x90 <Address 0x90 out of bounds>,
info=0xbf80ad30)
at ../../../../trunk/libstdc++-v3/libsupc++/eh_personality.cc:65
#1 0xb7ebf1e2 in __gxx_personality_v0 (version=1, actions=1,
exception_class=5138137972254386944,
ue_header=0x804a038, context=0xbf80ae54)
at ../../../../trunk/libstdc++-v3/libsupc++/eh_personality.cc:435
#2 0xb7dd18d1 in _Unwind_RaiseException (exc=0x804a038) at
../../trunk/gcc/unwind.inc:117
#3 0xb7ebf71d in __cxa_throw (obj=0x804a058, tinfo=0xb7eec494, dest=0xb7ebfb70
<~bad_alloc>)
at ../../../../trunk/libstdc++-v3/libsupc++/eh_throw.cc:71
#4 0xb7e53fb5 in std::__throw_bad_alloc () at
../../../../trunk/libstdc++-v3/src/functexcept.cc:52
#5 0x0804897c in
__gnu_test::check_allocate_max_size<__gnu_cxx::bitmap_allocator<int> > ()
at
/home/paolo/Gcc/svn-dirs/trunk-build/i686-pc-linux-gnu/libstdc++-v3/include/ext/bitmap_allocator.h:1050
#6 0x080489cc in main ()
at
/home/paolo/Gcc/svn-dirs/trunk/libstdc++-v3/testsuite/ext/bitmap_allocator/check_allocate_max_size.cc:30
--
Summary: FAIL: ext/bitmap_allocator/check_allocate_max_size.cc
execution test
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pcarlini at suse dot de
GCC target triplet: sh4-unknown-linux-gnu, x86_64-suse-linux-gnu/-m32, i686-
pc-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639