This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/49452] New: New testsuite failures with arm-linux-gnueabi comp-goto failing with
- From: "ramana at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 17 Jun 2011 11:55:19 +0000
- Subject: [Bug tree-optimization/49452] New: New testsuite failures with arm-linux-gnueabi comp-goto failing with
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49452
Summary: New testsuite failures with arm-linux-gnueabi
comp-goto failing with
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ramana@gcc.gnu.org
Host: i686-linux-gnu
Target: arm-linux-gnueabi
These failures have shown up in the last few days with arm-linux-gnueabi
FAIL: gcc.c-torture/execute/comp-goto-2.c execution, -O2
FAIL: gcc.c-torture/execute/comp-goto-2.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/comp-goto-2.c execution, -O3 -g
FAIL: gcc.c-torture/execute/comp-goto-2.c execution, -Os
FAIL: gcc.c-torture/execute/comp-goto-2.c execution, -O2 -flto
-flto-partition=none
FAIL: gcc.c-torture/execute/comp-goto-2.c execution, -O2 -flto
I haven't looked at in great detail yet to analyse what causes this problem but
it appears to have appeared in the last week or so.
GCC was configured as :
--target=arm-none-linux-gnueabi --enable-languages=c,c++,fortran
--with-cpu=cortex-a9 --with-fpu=neon --with-float=softfp
cheers
Ramana