target/6775: x86-64-netbsd compiler dies with SIGILL when using -Os
Jason R Thorpe
thorpej@wasabisystems.com
Thu May 23 20:55:00 GMT 2002
On Thu, May 23, 2002 at 10:46:05AM +0200, Jan Hubicka wrote:
> Hmm, looks like broken splitter. I will take a look later tonight.
FWIW, I think whatever is causing the x86-64 breakage is causing
test cases to fail for 32-bit x86, as well. This is from a "make check"
on i386-netbsdelf:
Executing on host: /u1/hack/gnu-toolchain/gcc/build/i386-i386/gcc/xgcc -B/u1/hac
k/gnu-toolchain/gcc/build/i386-i386/gcc/ -w -Os -c -o /u1/hack/gnu-toolchai
n/gcc/build/i386-i386/gcc/testsuite/20010117-2.o /u1/hack/gnu-toolchain/gcc/gcc/
gcc/testsuite/gcc.c-torture/compile/20010117-2.c (timeout = 300)
xgcc: Internal error: Illegal instruction (program cc1)^M
Please submit a full bug report.^M
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.^M
compiler exited with status 1
output is:
xgcc: Internal error: Illegal instruction (program cc1)^M
Please submit a full bug report.^M
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.^M
FAIL: gcc.c-torture/compile/20010117-2.c, -Os
...most of my test case failures seem to be like this:
Running /u1/hack/gnu-toolchain/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
FAIL: gcc.c-torture/compile/20010117-2.c, -Os
FAIL: gcc.c-torture/compile/20010518-1.c, -Os
FAIL: gcc.c-torture/compile/20011114-4.c, -Os
FAIL: gcc.c-torture/compile/920413-1.c, -Os
FAIL: gcc.c-torture/compile/920625-1.c, -Os
FAIL: gcc.c-torture/compile/920909-1.c, -Os
FAIL: gcc.c-torture/compile/930120-1.c, -Os
FAIL: gcc.c-torture/compile/950612-1.c, -Os
FAIL: gcc.c-torture/compile/950922-1.c, -Os
Running /u1/hack/gnu-toolchain/gcc/gcc/gcc/testsuite/gcc.c-torture/execute/execute.exp ...
FAIL: gcc.c-torture/execute/20000224-1.c compilation, -Os
FAIL: gcc.c-torture/execute/20001124-1.c compilation, -Os
FAIL: gcc.c-torture/execute/20011008-3.c compilation, -Os
FAIL: gcc.c-torture/execute/20020226-1.c compilation, -Os
FAIL: gcc.c-torture/execute/20020402-1.c execution, -Os
FAIL: gcc.c-torture/execute/20020508-1.c compilation, -Os
FAIL: gcc.c-torture/execute/20020508-2.c compilation, -Os
FAIL: gcc.c-torture/execute/20020508-3.c compilation, -Os
FAIL: gcc.c-torture/execute/920501-6.c compilation, -Os
FAIL: gcc.c-torture/execute/920731-1.c compilation, -Os
FAIL: gcc.c-torture/execute/921204-1.c compilation, -Os
FAIL: gcc.c-torture/execute/930818-1.c compilation, -Os
FAIL: gcc.c-torture/execute/931102-2.c compilation, -Os
FAIL: gcc.c-torture/execute/940122-1.c compilation, -Os
FAIL: gcc.c-torture/execute/960116-1.c compilation, -Os
.
.
.
Running /u1/hack/gnu-toolchain/gcc/gcc/gcc/testsuite/gcc.c-torture/unsorted/unsorted.exp ...
FAIL: gcc.c-torture/unsorted/BUG13.c, -Os
FAIL: gcc.c-torture/unsorted/bb1.c, -Os
FAIL: gcc.c-torture/unsorted/ex.c, -Os
FAIL: gcc.c-torture/unsorted/logic.c, -Os
FAIL: gcc.c-torture/unsorted/test.c, -Os
FAIL: gcc.c-torture/unsorted/udivmod4.c, -Os
..etc.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
More information about the Gcc-bugs
mailing list