[Bug middle-end/52650] [4.8 Regression] FAIL: gcc.dg/torture/pr51106-2.c * (internal compiler error)
ebotcazou at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Tue Nov 13 10:10:00 GMT 2012
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52650
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |ebotcazou at gcc dot
| |gnu.org
--- Comment #12 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-11-13 10:10:21 UTC ---
> So, which exact testcase still fails on which target with what options?
> Tried gcc.dg/torture/20090618-1.c with -O1 -m32 with sparc-linux cross and
> can't reproduce - foo contains
> add %sp, -96, %sp
> mov 1, %o0
> jmp %o7+8
> add %sp, 96, %sp
> which is correct.
There are no more execution failures on SPARC (modulo
gcc.dg/builtin-object-size-8.c). The only remaining failures are:
FAIL: gcc.dg/torture/pr51106-2.c -O0 (internal compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -O0 (test for excess errors)
FAIL: gcc.dg/torture/pr51106-2.c -O1 (internal compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -O1 (test for excess errors)
FAIL: gcc.dg/torture/pr51106-2.c -O2 (internal compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -O2 (test for excess errors)
FAIL: gcc.dg/torture/pr51106-2.c -O3 -fomit-frame-pointer (internal compiler
error)
FAIL: gcc.dg/torture/pr51106-2.c -O3 -fomit-frame-pointer (test for excess
errors)
FAIL: gcc.dg/torture/pr51106-2.c -O3 -g (internal compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -O3 -g (test for excess errors)
FAIL: gcc.dg/torture/pr51106-2.c -Os (internal compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -Os (test for excess errors)
FAIL: gcc.dg/torture/pr51106-2.c -O2 -flto -flto-partition=none (internal
compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -O2 -flto -flto-partition=none (test for
excess errors)
FAIL: gcc.dg/torture/pr51106-2.c -O2 -flto (internal compiler error)
FAIL: gcc.dg/torture/pr51106-2.c -O2 -flto (test for excess errors)
like everywhere else.
More information about the Gcc-bugs
mailing list