This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/49429] dse.c changes to fix PR44194 (r175063) cause execution failures
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 15 Jun 2011 23:11:06 +0000
- Subject: [Bug rtl-optimization/49429] dse.c changes to fix PR44194 (r175063) cause execution failures
- Auto-submitted: auto-generated
- References: <bug-49429-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49429
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu.org
--- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2011-06-15 23:10:36 UTC ---
I see this for cris-elf too. The full set of regressions for cris-elf
(last_worked:start_fail 175051:175064) are:
g++.sum g++.dg/torture/pr43879-1_1.C
gcc.sum gcc.c-torture/execute/20000412-3.c
gcc.sum gcc.c-torture/execute/20030914-1.c
gfortran.sum gfortran.dg/dependency_25.f90
gfortran.sum gfortran.dg/der_array_1.f90
gfortran.sum gfortran.dg/extends_3.f03
gfortran.sum gfortran.dg/structure_constructor_1.f03
As in:
Running
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.c-torture/execute/execute.exp ...
FAIL: gcc.c-torture/execute/20000412-3.c execution, -O1
FAIL: gcc.c-torture/execute/20030914-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20030914-1.c execution, -O3 -fomit-frame-pointer
-funroll-loops
FAIL: gcc.c-torture/execute/20030914-1.c execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20030914-1.c execution, -O3 -g
...
Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/torture/dg-torture.exp
...
FAIL: g++.dg/torture/pr43879-1_1.C -O1 execution test
FAIL: g++.dg/torture/pr43879-1_1.C -O2 execution test
FAIL: g++.dg/torture/pr43879-1_1.C -O3 -fomit-frame-pointer execution test
FAIL: g++.dg/torture/pr43879-1_1.C -O3 -g execution test
FAIL: g++.dg/torture/pr43879-1_1.C -Os execution test
...
Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
...
FAIL: gfortran.dg/dependency_25.f90 -O1 execution test
FAIL: gfortran.dg/dependency_25.f90 -O2 execution test
FAIL: gfortran.dg/dependency_25.f90 -Os execution test
FAIL: gfortran.dg/der_array_1.f90 -O1 execution test
FAIL: gfortran.dg/der_array_1.f90 -O2 execution test
FAIL: gfortran.dg/der_array_1.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/der_array_1.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/der_array_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/der_array_1.f90 -O3 -g execution test
FAIL: gfortran.dg/der_array_1.f90 -Os execution test
FAIL: gfortran.dg/extends_3.f03 -O1 execution test
...
FAIL: gfortran.dg/structure_constructor_1.f03 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/structure_constructor_1.f03 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
Messages in gcc.log and g++.log say the same thing (call to abort):
PASS: gcc.c-torture/execute/20000412-3.c compilation, -O1
program stopped with signal 6.
FAIL: gcc.c-torture/execute/20000412-3.c execution, -O1
And similarly in gfortran.log:
PASS: gfortran.dg/dependency_25.f90 -O1 (test for excess errors)
Backtrace not yet available on this platform, sorry!
program stopped with signal 6.
FAIL: gfortran.dg/dependency_25.f90 -O1 execution test