This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

gcc.c-torture/execute/ieee failures on alpha


The following failures in the test-suite on alphaev6-unknown-linux-gnu
bother me, because if I add -mieee to the options with, e.g., -O2,
then these programs don't abort.  I don't know how the testing framework
operates; is there some way to indicate that on alpha these need the
-mieee option to work?

This would get rid of over half the gcc failures on the alpha.

Brad

Running /export/u11/lucier/programs/egcs/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp ...
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O0
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O1
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O2
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O3 -fomit-frame-pointer 
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -O3 -g
FAIL: gcc.c-torture/execute/ieee/fp-cmp-2.c execution,  -Os
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution,  -O0
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution,  -O1
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution,  -O2
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution,  -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution,  -O3 -g
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution,  -Os


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]