Build and Check Problems with gcc 4.5.1: Bugs to Be Reported?

[Ian Lance Taylor]

Tom Browder <tom.browder@gmail.com> writes:

> I did get some "FAIL:" results but, according to some gcc
> instructions, they are not too significant.  However, I have repeated
> them here:
>
> FAIL: gcc.dg/guality/vla-1.c  -O0  line 17 sizeof (a) == 6
> FAIL: gcc.dg/guality/vla-1.c  -O0  line 24 sizeof (a) == 17 * sizeof (short)
> FAIL: gcc.dg/guality/vla-1.c  -O1  line 17 sizeof (a) == 6
> FAIL: gcc.dg/guality/vla-1.c  -O1  line 24 sizeof (a) == 17 * sizeof (short)
> FAIL: gcc.dg/guality/vla-1.c  -O2  line 17 sizeof (a) == 6
> FAIL: gcc.dg/guality/vla-1.c  -O2  line 24 sizeof (a) == 17 * sizeof (short)
> FAIL: gcc.dg/guality/vla-1.c  -O3 -fomit-frame-pointer  line 17 sizeof (a) == 6
> FAIL: gcc.dg/guality/vla-1.c  -O3 -fomit-frame-pointer  line 24 sizeof
> (a) == 17 * sizeof (short)
> FAIL: gcc.dg/guality/vla-1.c  -O3 -g  line 17 sizeof (a) == 6
> FAIL: gcc.dg/guality/vla-1.c  -O3 -g  line 24 sizeof (a) == 17 * sizeof (short)
> FAIL: gcc.dg/guality/vla-1.c  -Os  line 17 sizeof (a) == 6
> FAIL: gcc.dg/guality/vla-1.c  -Os  line 24 sizeof (a) == 17 * sizeof (short)
> FAIL: libmudflap.c/pass46-frag.c (-O2) (test for excess errors)
> FAIL: libmudflap.c/pass46-frag.c (-O2) (test for excess errors)
> FAIL: libmudflap.c/fail31-frag.c (-O3) output pattern test
> FAIL: libmudflap.c/pass45-frag.c (-O3) execution test
> FAIL: libmudflap.c/pass45-frag.c (-O3) output pattern test
> FAIL: libmudflap.c/pass45-frag.c (-O3) execution test
> FAIL: libmudflap.c/pass45-frag.c (-O3) output pattern test
> FAIL: libmudflap.c/pass46-frag.c (-O3) (test for excess errors)
> FAIL: libmudflap.c/pass46-frag.c (-O3) (test for excess errors)
> FAIL: libmudflap.c++/pass41-frag.cxx execution test
> FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
> FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
> FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test
> FAIL: abi_check
>
> My concerns are two:
>
> 1.  Should I be worried about the check results?
>
> 2.  Should I file a bug report for any or all of these problems?

One approach is to look at http://gcc.gnu.org/ml/gcc-testresults/ to see
if the automated testers see similar errors for your target.  If they
do, then there is nothing to worry about.

The libmudflap tests are a little flaky in my experience.  I'm not sure
about the guality or abi_check test failure, though.

Ian