This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
New sparcv9 testsuite failure gcc.c-torture/execute/20000511-1.c
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- To: "David S. Miller" <davem at redhat dot com>
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 19 Jun 2002 21:23:47 +0200 (MEST)
- Subject: New sparcv9 testsuite failure gcc.c-torture/execute/20000511-1.c
Comparing sparc-sun-solaris2.8 testsuite results, I noticed that between
LAST_UPDATED: Sat Jun 1 15:45:51 UTC 2002
http://gcc.gnu.org/ml/gcc-testresults/2002-06/msg00023.html
and
LAST_UPDATED: Sun Jun 2 17:03:15 UTC 2002
http://gcc.gnu.org/ml/gcc-testresults/2002-06/msg00060.html
a couple of new testsuite failures occur for either sparcv9 or sparc -m64
configurations:
FAIL: gcc.c-torture/execute/20000511-1.c compilation, -O1
UNRESOLVED: gcc.c-torture/execute/20000511-1.c execution, -O1
FAIL: gcc.c-torture/execute/20000511-1.c compilation, -O2
UNRESOLVED: gcc.c-torture/execute/20000511-1.c execution, -O2
FAIL: gcc.c-torture/execute/20000511-1.c compilation, -O3 -fomit-frame-pointer
UNRESOLVED: gcc.c-torture/execute/20000511-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20000511-1.c compilation, -O3 -g
UNRESOLVED: gcc.c-torture/execute/20000511-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20000511-1.c compilation, -Os
UNRESOLVED: gcc.c-torture/execute/20000511-1.c execution, -Os
Those tests fail to link:
Executing on host: /amnt/figaro/volumes/obj-gcc/gcc/obj.sol2/gcc-3.2-20020617/8-gcc-no-ada/gcc/xgcc -B/amnt/figaro/volumes/obj-gcc/gcc/obj.sol2/gcc-3.2-20020617/8-gcc-no-ada/gcc/ /vol/gnu/src/gcc/gcc/gcc/testsuite/gcc.c-torture/execute/20000511-1.c -w -O1 -lm -m64 -o /vol/gcc/obj/gcc-3.2-20020617/8-gcc-no-ada/gcc/testsuite/20000511-1.x1 (timeout = 300)
spawn /amnt/figaro/volumes/obj-gcc/gcc/obj.sol2/gcc-3.2-20020617/8-gcc-no-ada/gcc/xgcc -B/amnt/figaro/volumes/obj-gcc/gcc/obj.sol2/gcc-3.2-20020617/8-gcc-no-ada/gcc/ /vol/gnu/src/gcc/gcc/gcc/testsuite/gcc.c-torture/execute/20000511-1.c -w -O1 -lm -m64 -o /vol/gcc/obj/gcc-3.2-20020617/8-gcc-no-ada/gcc/testsuite/20000511-1.x1
Undefined first referenced
symbol in file
.rem /var/tmp//ccW5fNge.o
ld: fatal: Symbol referencing errors. No output written to /vol/gcc/obj/gcc-3.2-20020617/8-gcc-no-ada/gcc/testsuite/20000511-1.x1
collect2: ld returned 1 exit status
compiler exited with status 1
.rem is only in the 32-bit libc and shouldn't be used for 64-bit
compilations.
The culprit patch still needs to be determined.
Rainer