public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Thomas Pinski <pinskia@gmail.com>
To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: Re: [Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap
Date: Sat, 15 Nov 2008 22:15:00 -0000	[thread overview]
Message-ID: <168318E3-C324-4693-9B08-5983A6A9A946@gmail.com> (raw)
In-Reply-To: <20081115215949.6617.qmail@sourceware.org>



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
>


  reply	other threads:[~2008-11-15 22:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 21:28 [Bug rtl-optimization/38139] New: " edwintorok at gmail dot com
2008-11-15 21:40 ` [Bug rtl-optimization/38139] " edwintorok at gmail dot com
2008-11-15 21:51 ` [Bug rtl-optimization/38139] New: " Andrew Thomas Pinski
2008-11-15 21:52 ` [Bug rtl-optimization/38139] " pinskia at gmail dot com
2008-11-15 22:01 ` edwintorok at gmail dot com
2008-11-15 22:15   ` Andrew Thomas Pinski [this message]
2008-11-15 22:16 ` pinskia at gmail dot com
2008-11-16  6:42 ` ebotcazou at gcc dot gnu dot org

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=168318E3-C324-4693-9B08-5983A6A9A946@gmail.com \
    --to=pinskia@gmail.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@gcc.gnu.org \
    /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).