Re: GCC 4.0 RC1 Available

[Julian Brown <julian at codesourcery dot com>]

On 2005-04-11, Julian Brown <julian@codesourcery.com> wrote:
> On 2005-04-10, Mark Mitchell <mark@codesourcery.com> wrote:
>>
>>      * The DejaGNU testsuite has been run, and compared with a run of 
>> the testsuite on the previous release of GCC, and no regressions are 
>> observed.
>>
>> If you are willing to help, please download the release candidate, build 
>> it on appropriate platforms, and post testresults by using 
>> contrib/test_summary.  Please use the release candidate itself, *not* 
>> the CVS 4.0 release branch, as part of the goal is to ensure that the 
>> packaging scripts are working.
>
> For arm-none-elf (cross from i686-pc-linux-gnu), with binutils and newlib
> from CVS:
>
>   http://gcc.gnu.org/ml/gcc-testresults/2005-04/msg00800.html
>
> And, for comparison, 3.4.3 tests:
>
>   http://gcc.gnu.org/ml/gcc-testresults/2005-04/msg00799.html
>
> Quite a few of the 4.0 RC1 tests FAIL, though I'm not sure how many of
> these are regressions, and how many are just new tests which fail.

In more detail, for gcc.sum:

Tests that now fail, but worked before:

gcc.c-torture/execute/bitfld-1.c execution,  -O0
gcc.c-torture/execute/bitfld-1.c execution,  -O1
gcc.c-torture/execute/bitfld-1.c execution,  -O2
gcc.c-torture/execute/bitfld-1.c execution,  -O3 -fomit-frame-pointer
gcc.c-torture/execute/bitfld-1.c execution,  -O3 -g
gcc.c-torture/execute/bitfld-1.c execution,  -Os
gcc.c-torture/execute/builtin-constant.c execution,  -O1
gcc.dg/array-5.c bad vla handling (test for bogus messages, line 40)
gcc.dg/bitfld-2.c  (test for warnings, line 14)
gcc.dg/bitfld-2.c  (test for warnings, line 15)
gcc.dg/bitfld-2.c  (test for warnings, line 20)
gcc.dg/bitfld-2.c  (test for warnings, line 21)
gcc.dg/builtins-18.c (test for excess errors)
gcc.dg/builtins-20.c (test for excess errors)
gcc.dg/const-elim-1.c scan-assembler-not L\\$?C[^A-Z]
gcc.dg/cpp/trad/include.c (test for excess errors)
gcc.dg/redecl-1.c  (test for errors, line 67)
gcc.dg/sequence-pt-1.c sequence point warning (test for warnings, line 59)
gcc.dg/uninit-1.c uninitialized variable warning (test for bogus messages,
line 16)
gcc.dg/uninit-2.c uninitialized variable warning (test for bogus messages,
line 28)
gcc.dg/uninit-3.c uninitialized variable warning (test for bogus messages,
line 11)
gcc.dg/uninit-8.c uninitialized variable warning (test for bogus messages,
line 14)
gcc.dg/Wunreachable-1.c (test for excess errors)


For g++.sum:

Tests that now fail, but worked before:

g++.dg/other/error8.C duplicate error messages (test for bogus messages, line
8)
g++.dg/other/error8.C duplicate error messages (test for bogus messages, line
9)
g++.dg/rtti/tinfo1.C scan-assembler-not
.section[^\n\r]*_ZTIP9CTemplateIhE[^\n\r
]*
g++.dg/template/nested3.C  (test for errors, line 12)
g++.dg/template/nested3.C  (test for errors, line 14)
g++.dg/template/nested3.C  (test for errors, line 25)
g++.dg/template/nested3.C  (test for errors, line 8)
g++.old-deja/g++.jason/cond.C  (test for errors, line 20)
g++.old-deja/g++.jason/cond.C  (test for errors, line 22)
g++.old-deja/g++.jason/cond.C  (test for errors, line 25)
g++.old-deja/g++.jason/cond.C  (test for errors, line 27)
g++.old-deja/g++.oliva/expr2.C execution test
g++.old-deja/g++.oliva/template10.C  (test for errors, line 22)
g++.old-deja/g++.other/decl5.C  (test for warnings, line 55)
g++.old-deja/g++.other/decl5.C  (test for warnings, line 56)


For libstdc++.sum:

Tests that now fail, but worked before:

27_io/basic_filebuf/open/char/9507.cc (test for excess errors)


That's a total of about 39 regressions, I think. I also got quite a few
"Old tests that passed, that have disappeared" results. Is that expected?

Julian