This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/49757] New: FAIL: gcc.target/tic6x/*.c
- From: "hjl.tools at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 Jul 2011 12:05:33 +0000
- Subject: [Bug testsuite/49757] New: FAIL: gcc.target/tic6x/*.c
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49757
Summary: FAIL: gcc.target/tic6x/*.c
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
CC: bernds@codesourcery.com
On Linux/x86, revision 176310 gave:
FAIL: gcc.target/tic6x/builtins/extclr.c -O0 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O1 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O2 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O2 -flto (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O2 -flto -flto-partition=none (test
for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O3 -fomit-frame-pointer (test for
excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O3 -fomit-frame-pointer
-funroll-loops (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -O3 -g (test for excess errors)
FAIL: gcc.target/tic6x/builtins/extclr.c -Os (test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O0 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O1 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O2 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O2 -flto (test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O2 -flto -flto-partition=none
(test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O3 -fomit-frame-pointer (test for
excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -O3 -g (test for excess errors)
FAIL: gcc.target/tic6x/builtins/sarith1.c -Os (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O0 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O1 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O2 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O2 -flto (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O2 -flto -flto-partition=none (test
for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O3 -fomit-frame-pointer (test for
excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -O3 -g (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpy.c -Os (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O0 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O1 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O2 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O2 -flto (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O2 -flto -flto-partition=none (test
for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O3 -fomit-frame-pointer (test for
excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -O3 -g (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpyh.c -Os (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O0 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O1 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O2 (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O2 -flto (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O2 -flto -flto-partition=none (test
for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O3 -fomit-frame-pointer (test for
excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -O3 -g (test for excess errors)
FAIL: gcc.target/tic6x/builtins/smpylh.c -Os (test for excess errors)
Why do we run TIC6X tests on Linux/x86?