This is the mail archive of the gcc@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]

loop-2{f,g} failures

I have been adding another x86 target (essentially a SVR5-based target)
and trying to analyze two new failures that I haven't been seeing on
other similar x86 targets.  Linux doesn't fail.  OpenServer doesn't fail.
Unixware 2 doesn't fail.

The tests in question were loop-2f and loop-2g.  Now I see these exact
tests failing on Sparc/Solaris tests.  I think this means I can pretty
much quit staring at my new target-specific files. :-)

Can anyone briefly comment on these failures?  Are these known to be
fragile? In all the mmap voodoo in those test cases, have we perhaps
introduced a dependence on library/mmap/vm behaviour?


Thanx,
RJL


Matthias Mueller wrote:
> Native configuration is sparc-sun-solaris2.5.1
> 
> 		=== gcc tests ===
> 
> 
> Running target unix
> FAIL: gcc.c-torture/execute/980506-2.c execution,  -O2 
> FAIL: gcc.c-torture/execute/980506-2.c execution,  -O2 -g 
> FAIL: gcc.c-torture/execute/980506-2.c execution,  -Os 
> FAIL: gcc.c-torture/execute/980526-1.c execution,  -O2 -fomit-frame-pointer -finline-functions 
> FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 
> FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions 
> FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
> FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 
> FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -g 
> FAIL: gcc.c-torture/execute/loop-2f.c execution,  -Os 
> FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O2 
> FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O2 -fomit-frame-pointer -finline-functions 
> FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
> FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 
> FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O2 -g 
> FAIL: gcc.c-torture/execute/loop-2g.c execution,  -Os 
> FAIL: gcc.dg/980626-1.c (test for excess errors)
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]