From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-54561-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 32576 invoked by alias); 13 Dec 2013 10:28:34 -0000
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
Received: (qmail 32566 invoked by uid 89); 13 Dec 2013 10:28:33 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ie0-f178.google.com
Received: from mail-ie0-f178.google.com (HELO mail-ie0-f178.google.com) (209.85.223.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 13 Dec 2013 10:28:32 +0000
Received: by mail-ie0-f178.google.com with SMTP id lx4so2500447iec.37        for <gcc-help@gcc.gnu.org>; Fri, 13 Dec 2013 02:28:30 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.12.71 with SMTP id w7mr2421300igb.32.1386930510601; Fri, 13 Dec 2013 02:28:30 -0800 (PST)
Received: by 10.64.98.34 with HTTP; Fri, 13 Dec 2013 02:28:30 -0800 (PST)
In-Reply-To: <CADj25HOU1NRhe80tkgcLNfU7qX1rqhWNg=6OMp33J7FbCKR__w@mail.gmail.com>
References: <CAL0afKsjuW5xQYZnRrC7E-LZaQp-AeVTL1-KzkDetfsB7iQq2Q@mail.gmail.com>	<CADj25HOSs-_p6Lj-qOLdQdcu4_Z+kT=kE0fQBJxN1tG8+noj1w@mail.gmail.com>	<CAL0afKujtbGmpLUM-f35R4KBCipA2_rkKYb_=rrJAYh_a=HCug@mail.gmail.com>	<CADj25HOU1NRhe80tkgcLNfU7qX1rqhWNg=6OMp33J7FbCKR__w@mail.gmail.com>
Date: Fri, 13 Dec 2013 10:28:00 -0000
Message-ID: <CAH6eHdQnTXK8z_ZSXNT3y_ut_WBtUaTY9gCvC96Oo1cDVxeLwQ@mail.gmail.com>
Subject: Re: Errors on testing GCC 4.6.4 compilation
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>
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
X-SW-Source: 2013-12/txt/msg00098.txt.bz2

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.