From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Chung-Ju Wu <jasonwucj@gmail.com>
Cc: Derrick Lin <klin938@gmail.com>, gcc <gcc-help@gcc.gnu.org>
Subject: Re: Errors on testing GCC 4.6.4 compilation
Date: Fri, 13 Dec 2013 10:28:00 -0000 [thread overview]
Message-ID: <CAH6eHdQnTXK8z_ZSXNT3y_ut_WBtUaTY9gCvC96Oo1cDVxeLwQ@mail.gmail.com> (raw)
In-Reply-To: <CADj25HOU1NRhe80tkgcLNfU7qX1rqhWNg=6OMp33J7FbCKR__w@mail.gmail.com>
On 13 December 2013 08:49, Chung-Ju Wu <jasonwucj@gmail.com> wrote:
> 2013/12/12 Derrick Lin <klin938@gmail.com>:
>> 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.
prev parent reply other threads:[~2013-12-13 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 0:40 Derrick Lin
2013-12-11 6:35 ` Chung-Ju Wu
2013-12-11 22:21 ` Derrick Lin
2013-12-13 8:50 ` Chung-Ju Wu
2013-12-13 10:28 ` Jonathan Wakely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH6eHdQnTXK8z_ZSXNT3y_ut_WBtUaTY9gCvC96Oo1cDVxeLwQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jasonwucj@gmail.com \
--cc=klin938@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).