From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toon Moene To: law@cygnus.com Cc: egcs@cygnus.com Subject: Re: 1.0.3 pre-release available Date: Sun, 26 Apr 1998 08:21:00 -0000 Message-id: <9804261449.AA17362@moene.indiv.nluug.nl> References: <18538.893574081@hurl.cygnus.com> X-SW-Source: 1998-04/msg01037.html > I've made the egcs-1.0.3 prerelease available. > * Fix typo in libio (HJ -- can you be more specific about > what exactly you fixed?) > * Fix the Fortran negative array index problem (again). This indeed seems to be fixed (see below). > * Fix a few Alpha code generation and compiler abort problems > exposed by RedHat 5.1. So there were Linux/Alpha problems ? Shees, means that Joe was right after all - perhaps I missed it due to the ix86 advocates being so much more vocal (gives a whole new meaning to "devils advocate" :-) > * Fix 2 x86 code generation bugs exposed by glibc2 and > RedHat 5.1. > * Fix rs6000/ppc bug when converting from values from integer > types to floating point types in frameless functions. This is what I got on a "Red Hat Linux release 4.2 (Biltmore)" Alpha system (alphaev56-unknown-linux-gnulibc1 according to configure). Build & compare without problems. Result of make -k check: === libio tests === === libio Summary === # of expected passes 40 === libstdc++ tests === FAIL: tstring.cc compilation FAIL: tstring.cc -O compilation === libstdc++ Summary === # of expected passes 24 # of unexpected failures 2 # of expected failures 4 === gcc tests === FAIL: gcc.c-torture/execute/960218-1.c execution, -O0 FAIL: gcc.c-torture/execute/960218-1.c execution, -O1 FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops FAIL: gcc.c-torture/execute/complex-5.c execution, -O0 FAIL: gcc.c-torture/execute/complex-5.c execution, -O1 FAIL: gcc.c-torture/execute/complex-5.c execution, -O2 FAIL: gcc.c-torture/execute/complex-5.c execution, -O2 -fomit-frame-pointer -finline-functions FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O0 FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O1 FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O2 FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O2 -fomit-frame-pointer -finline-functions === gcc Summary === # of expected passes 4856 # of unexpected failures 14 # of expected failures 5 # of unsupported tests 9 === g++ tests === FAIL: g++.benjamin/p12475.C (test for warnings, line 4) XPASS: g++.brendan/array1.C overflow in array dimension.* , (test for errors, line 6) XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38) XPASS: g++.mike/dyncast1.C Execution test XPASS: g++.mike/dyncast2.C Execution test FAIL: g++.mike/eh39.C Execution test FAIL: g++.mike/eh40.C Execution test === g++ Summary === # of expected passes 3388 # of unexpected failures 3 # of unexpected successes 4 # of expected failures 82 # of untested testcases 10 === g77 tests === FAIL: g77.f-torture/execute/dnrm2.f execution, -O0 FAIL: g77.f-torture/execute/dnrm2.f execution, -O1 === g77 Summary === # of expected passes 130 # of unexpected failures 2 Furthermore, I tried the following Fortran example, which fails with egcs-1.0.2: program rotor implicit none integer KaKc(0:5,-5:5,0:2) integer cj call setkac( KaKc, 5 ) stop end c --------------------------------------------- subroutine setkac( KaKc, Jmax ) implicit none integer Jmax integer KaKc( 0:Jmax, -Jmax:Jmax, 0:2 ) integer cj, i cj = 0 i = -cj KaKc( cj, i, 1 ) = 0 write(*,*) 'Here we go !' KaKc( cj, -cj, 1 ) = 0 return end which would bomb after the message "Here we go !", and now completes succesfully. Cheers, Toon.