Results for egcs-2.93.04 19990131 (gcc2 ss-980929 experimental) testsuite...

[N8TM@aol.com]

In a message dated 2/10/99 8:51:09 PM Pacific Standard Time,
khan@xraylith.wisc.EDU writes:

<< 		=== g77 tests ===
 
 FAIL: g77.f-torture/execute/980628-0.f execution,  -O1 
 FAIL: g77.f-torture/execute/980628-3.f execution,  -O1 
 FAIL: g77.f-torture/execute/auto0.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-loops 
 FAIL: g77.f-torture/execute/auto0.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops 
 FAIL: g77.f-torture/execute/auto1.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-loops 
 FAIL: g77.f-torture/execute/auto1.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops 
 FAIL: g77.f-torture/execute/dnrm2.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-loops 
 FAIL: g77.f-torture/execute/dnrm2.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops 
FAIL: g77.f-torture/execute/short.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-loops 
FAIL: g77.f-torture/execute/short.f execution,  -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops   >>


All of these test failures began to occur on various other architectures since
the egcs-2.93.04 release, so I think they aren't specific to cygwin.  Everyone
who has presented hpux results on 2.93.04 and 2.93.06 has reported all of
these failures and more, and they all produce the failure of the first
assertion in gcc/f/target.c when run on hpux. I wonder if that assertion is
written portably; maybe it should fail on all architectures in the presence of
this bug.  The last 8 have turned up on more than one version of Irix and
86-linux.  All the more reason why they need fixing, as this g77 is unuseable
on any of these targets.