[Bug rtl-optimization/38139] New: --enable-checking=all times out during bootstrap

[Bug rtl-optimization/38139] New: --enable-checking=all times out during bootstrap

[edwintorok at gmail dot com]

I tried to build a gcc 4.4.0 with --enable-checking=all but it timed out:

$ /home/edwin/gcc-obj/./prev-gcc/xgcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc/configure --disable-multilib --disable-static
--prefix=/home/edwin/gcc_inst/ --enable-languages=c,c++ --enable-checking=all
Thread model: posix
gcc version 4.4.0 20081115 (experimental) [trunk revision 141891] (GCC)

xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [insn-emit.o] Error 1
make[3]: *** Waiting for unfinished jobs....
xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [insn-recog.o] Error 1
make[2]: *** [all-stage2-gcc] Error 2
make[1]: *** [stage2-bubble] Error 2

^it was building insn-emit and insn-recog in parallel, both timed out.

I was running it under ulimit  with a one hour timeout:
ulimit -t 3600 -v 1048576
make -j4 >makelog 2>makelog2

CPU is Intel(R) Core(TM)2 Quad  CPU   Q9550  @ 2.83GHz, 4GB RAM.

I know that --enable-checking=all is very slow, but it should take less than an
hour to compile insn-emit.o, shouldn't it?


-- 
           Summary: --enable-checking=all times out during bootstrap
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: edwintorok at gmail dot com
 GCC build triplet: x86_64-linux-gnu
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu


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

[Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap

[edwintorok at gmail dot com]

-- 

edwintorok at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor


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

Re: [Bug rtl-optimization/38139] New: --enable-checking=all times out during bootstrap

[Andrew Thomas Pinski]

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.

>
>
> $ /home/edwin/gcc-obj/./prev-gcc/xgcc -v
> Using built-in specs.
> Target: x86_64-unknown-linux-gnu
> Configured with: ../gcc/configure --disable-multilib --disable-static
> --prefix=/home/edwin/gcc_inst/ --enable-languages=c,c++ --enable- 
> checking=all
> Thread model: posix
> gcc version 4.4.0 20081115 (experimental) [trunk revision 141891]  
> (GCC)
>
> xgcc: Internal error: Killed (program cc1)
> Please submit a full bug report.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[3]: *** [insn-emit.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> xgcc: Internal error: Killed (program cc1)
> Please submit a full bug report.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[3]: *** [insn-recog.o] Error 1
> make[2]: *** [all-stage2-gcc] Error 2
> make[1]: *** [stage2-bubble] Error 2
>
> ^it was building insn-emit and insn-recog in parallel, both timed out.
>
> I was running it under ulimit  with a one hour timeout:
> ulimit -t 3600 -v 1048576
> make -j4 >makelog 2>makelog2
>
> CPU is Intel(R) Core(TM)2 Quad  CPU   Q9550  @ 2.83GHz, 4GB RAM.
>
> I know that --enable-checking=all is very slow, but it should take  
> less than an
> hour to compile insn-emit.o, shouldn't it?
>
>
> -- 
>           Summary: --enable-checking=all times out during bootstrap
>           Product: gcc
>           Version: 4.4.0
>            Status: UNCONFIRMED
>          Severity: normal
>          Priority: P3
>         Component: rtl-optimization
>        AssignedTo: unassigned at gcc dot gnu dot org
>        ReportedBy: edwintorok at gmail dot com
> GCC build triplet: x86_64-linux-gnu
>  GCC host triplet: x86_64-linux-gnu
> GCC target triplet: x86_64-linux-gnu
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38139
>

[Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap

[pinskia at gmail dot com]

------- Comment #1 from pinskia at gmail dot com  2008-11-15 21:51 -------
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.

>
>
> $ /home/edwin/gcc-obj/./prev-gcc/xgcc -v
> Using built-in specs.
> Target: x86_64-unknown-linux-gnu
> Configured with: ../gcc/configure --disable-multilib --disable-static
> --prefix=/home/edwin/gcc_inst/ --enable-languages=c,c++ --enable- 
> checking=all
> Thread model: posix
> gcc version 4.4.0 20081115 (experimental) [trunk revision 141891]  
> (GCC)
>
> xgcc: Internal error: Killed (program cc1)
> Please submit a full bug report.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[3]: *** [insn-emit.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> xgcc: Internal error: Killed (program cc1)
> Please submit a full bug report.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[3]: *** [insn-recog.o] Error 1
> make[2]: *** [all-stage2-gcc] Error 2
> make[1]: *** [stage2-bubble] Error 2
>
> ^it was building insn-emit and insn-recog in parallel, both timed out.
>
> I was running it under ulimit  with a one hour timeout:
> ulimit -t 3600 -v 1048576
> make -j4 >makelog 2>makelog2
>
> CPU is Intel(R) Core(TM)2 Quad  CPU   Q9550  @ 2.83GHz, 4GB RAM.
>
> I know that --enable-checking=all is very slow, but it should take  
> less than an
> hour to compile insn-emit.o, shouldn't it?
>
>
> -- 
>           Summary: --enable-checking=all times out during bootstrap
>           Product: gcc
>           Version: 4.4.0
>            Status: UNCONFIRMED
>          Severity: normal
>          Priority: P3
>         Component: rtl-optimization
>        AssignedTo: unassigned at gcc dot gnu dot org
>        ReportedBy: edwintorok at gmail dot com
> GCC build triplet: x86_64-linux-gnu
>  GCC host triplet: x86_64-linux-gnu
> GCC target triplet: x86_64-linux-gnu
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38139
>


-- 


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

[Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap

[edwintorok at gmail dot com]

------- 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?

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

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

Re: [Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap

[Andrew Thomas Pinski]

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
>

[Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap

[pinskia at gmail dot com]

------- 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

[Bug rtl-optimization/38139] --enable-checking=all times out during bootstrap

[ebotcazou at gcc dot gnu dot org]

------- Comment #4 from ebotcazou at gcc dot gnu dot org  2008-11-16 06:40 -------
> 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.

RTL checking is in fact moderately expensive, I use it all the time.  But fold
checking is quite expensive and *not* enabled by default.


-- 

ebotcazou at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX


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