http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
--- Comment #6 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-05
12:03:46 UTC ---
(In reply to comment #3)
> RE:
> > Your PC is broken.
> Comments such as these don't help much.
Indeed.
However, your bug report wasn't very useful either before you shared your
configuration. There are some hints for what's needed for GCC developers to
understand and investigate a bug in the web pages: http://gcc.gnu.org/bugs/
> > C only build with 3 stages takes about 18 minutes with -j2
> > on my PC.
>
> And what type of super-computer is that ?
For me it's a HP Pavilion dv9000 and it takes just over 20 minutes.
> > Compilation of small count of big files is faster than big count of small
> > files.
>
> Not in my experience. Why force such huge memory resource demands ?
I think it's due to --enable-stage1-checking=all. This enables a bunch of
really expensive checks.
> I guess as usual no help is to be expected from gcc-bugs - I'll have to
> modify genemit.c myself.
I don't know what you suppose to accomplish with this snide.
