From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-266686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 3703 invoked by alias); 15 Nov 2008 22:16:28 -0000
Received: (qmail 22976 invoked by alias); 15 Nov 2008 22:15:05 -0000
Date: Sat, 15 Nov 2008 22:16:00 -0000
Message-ID: <20081115221505.22974.qmail@sourceware.org>
X-Bugzilla-Reason: CC
References: <bug-38139-15165@http.gcc.gnu.org/bugzilla/>
Subject: [Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap
In-Reply-To: <bug-38139-15165@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "pinskia at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2008-11/txt/msg01260.txt.bz2



------- Comment #3 from pinskia at gmail dot com  2008-11-15 22:15 -------
Subject: Re:  --enable-checking=all times out during bootstrap



Sent from my iPhone

On Nov 15, 2008, at 1:59 PM, "edwintorok at gmail dot com"
<gcc-bugzilla@gcc.gnu.org 
 > wrote:

>
>
> ------- Comment #2 from edwintorok at gmail dot com  2008-11-15  
> 21:59 -------
> (In reply to comment #1)
>> Subject: Re:   New: --enable-checking=all times out during bootstrap
>>
>>
>>
>> Sent from my iPhone
>>
>> On Nov 15, 2008, at 1:27 PM, "edwintorok at gmail dot com"
>> <gcc-bugzilla@gcc.gnu.org
>>> wrote:
>>
>>> I tried to build a gcc 4.4.0 with --enable-checking=all but it timed
>>> out:
>>
>> Since --enable-checking=all enables gc all the time then yes
>> It will take a long time. Maybe even days. Marking is expensive.
>>
>
> Thanks, this is the 'gcac' flag, right?
>
Yes.

> What if I build with  
> "assert,df,fold,rtl,misc,tree,gc,rtlflag,runtime", would
> that build within a reasonable amount of time?

Rtl checking is also expensive (no way near as expensive as gcac) but  
it does find real bugs in some cases. Everything else is enabled by  
default during development of the trunk.

>
>
> And is it worth to build with more checking, than those enabled by  
> default?
> [i.e. did that expose bugs in the past?]



>
>
>
> -- 
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38139
>


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38139