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

Brad Lucier lucier@math.purdue.edu
Fri Dec 31 20:54:00 GMT 1999


The message

http://gcc.gnu.org/ml/gcc-patches/1999-04/msg01023.html

contains the following suggestion by rth:

... dejagnu's $prefix/share/dejagnu/baseboards/unix.exp
should contain

        if { [ istarget "alpha-*-*" ] } {
                set_board_info ieee_multilib_flags "-mieee";
        }

This was never implemented; Jeff Law suggested in another email
in that thread that it can wait until after the release of 1.1.2 ;-).
It's not in dejagnu-19990614 as distributed on the gcc site.

When tested properly with -mieee, the failures I noted in my
previous e-mail (and listed below) go away, but new ones arise:

> FAIL: gcc.c-torture/execute/ieee/rbug.c execution,  -O0 
> FAIL: gcc.c-torture/execute/ieee/rbug.c execution,  -O1 
> FAIL: gcc.c-torture/execute/ieee/rbug.c execution,  -O2 
> FAIL: gcc.c-torture/execute/ieee/rbug.c execution,  -O3 -fomit-frame-pointer 
> FAIL: gcc.c-torture/execute/ieee/rbug.c execution,  -O3 -g 
> FAIL: gcc.c-torture/execute/ieee/rbug.c execution,  -Os 

So the misconfiguration of dejagnu is not only generating false
positives, it's masking some real failures. Maybe Richard knows about
these, because he claims he has

 set_board_info ieee_multilib_flags "-mieee";

in unix.exp on his alphas, but it would be better if other people
saw these errors, too.

Brad Lucier

> 
> 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
> 



More information about the Gcc-bugs mailing list