[Bug java/41260] [4.5 Regression] major regressions in libjava testsuite between 4.4.1 and gcc trunk caused by r147995

["howarth at nitro dot med dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #12 from howarth at nitro dot med dot uc dot edu  2009-09-05 15:25 -------
In r147989, we had no regressions in x86_64-apple-darwin10 in the g++
testsuite. However, in r148013 (which is after the fix for PR 40304), we have
the following g++ testsuite failures which still exist in gcc trunk on
x86_64-apple-darwin10...

FAIL: g++.dg/cpp0x/variadic73.C execution test
FAIL: g++.dg/eh/delayslot1.C execution test
FAIL: g++.dg/eh/ia64-2.C execution test
FAIL: g++.dg/eh/simd-1.C execution test
FAIL: g++.dg/eh/simd-2.C execution test
FAIL: g++.dg/eh/synth2.C execution test
FAIL: g++.dg/ext/cleanup-8.C execution test
FAIL: g++.dg/ext/cleanup-9.C execution test
FAIL: g++.dg/init/array16.C execution test
FAIL: g++.dg/init/array5.C execution test
FAIL: g++.dg/init/ref9.C execution test
FAIL: g++.dg/opt/eh2.C execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O0  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O1  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O2  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O3 -fomit-frame-pointer 
execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/throw-1.C  -O0  execution test
FAIL: g++.dg/torture/stackalign/throw-1.C  -O1  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O0  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O1  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O2  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O3 -fomit-frame-pointer 
execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/throw-1.C  -O0  execution test
FAIL: g++.dg/torture/stackalign/throw-1.C  -O1  execution test
FAIL: g++.old-deja/g++.abi/cxa_vec.C execution test
FAIL: g++.old-deja/g++.eh/badalloc1.C execution test
FAIL: g++.old-deja/g++.eh/rethrow3.C execution test
FAIL: g++.old-deja/g++.eh/vbase2.C execution test
FAIL: g++.old-deja/g++.martin/new1.C execution test
FAIL: g++.old-deja/g++.mike/eh2.C execution test
FAIL: g++.old-deja/g++.mike/eh29.C execution test
FAIL: g++.old-deja/g++.mike/eh41.C execution test
FAIL: g++.old-deja/g++.mike/eh44.C execution test
FAIL: g++.old-deja/g++.oliva/delete3.C execution test
FAIL: g++.old-deja/g++.other/array1.C execution test
FAIL: g++.old-deja/g++.other/init7.C execution test
FAIL: g++.old-deja/g++.other/singleton.C execution test
FAIL: g++.old-deja/g++.robertl/eb50.C execution test
FAIL: g++.old-deja/g++.robertl/eh990323-5.C execution test

Any idea of which of these would present the easy opportunity for debugging the
problem?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260