Re: Errors on testing GCC 4.6.4 compilation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 13 December 2013 08:49, Chung-Ju Wu <jasonwucj@xxxxxxxxx> wrote:
> 2013/12/12 Derrick Lin <klin938@xxxxxxxxx>:
>> Thanks Jason,
>>
>> I took a look at the gcc.log and found some failures. Am I supposed to
>> fix them all so that my gcc's considered a good built?
>>
>> FAIL: gcc.c-torture/compile/limits-exprparen.c  -O0  (internal compiler error)
>> FAIL: gcc.c-torture/compile/limits-exprparen.c  -O0  (test for excess errors)
> [...]
>> XFAIL: gcc.dg/Wtype-limits.c  (test for bogus messages, line 16)
>> XFAIL: gcc.dg/Wtype-limits.c  (test for bogus messages, line 64)
>
> Hi, Derrick,
>
> Refer to:
>   http://www.delorie.com/gnu/docs/dejagnu/dejagnu_6.html
>
> XFAIL means it is a expected fail case.
> Generally you can ignore them.
>
> For the FAIL cases, yes, you need to figure out why they
> are failed on your environment.  And then decide whether
> you want to fix them.

You can ignore FAIL results in gcc.dg/guality and libmudflap, they do
not indicare a problem with the build.




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux