This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.1: Buildable on GHz machines only?
- From: Richard Earnshaw <rearnsha at gcc dot gnu dot org>
- To: Robert Dewar <dewar at adacore dot com>
- Cc: Peter Barada <peter at the-baradas dot com>, Joe dot Buck at synopsys dot COM, hjl at lucon dot org, aph at redhat dot com, aoliva at redhat dot com, dje at watson dot ibm dot com, schwab at suse dot de, pinskia at physics dot uc dot edu, pkoning at equallogic dot com, s dot bosscher at student dot tudelft dot nl, gcc at gcc dot gnu dot org, matt at 3am-software dot com, cow at compsoc dot man dot ac dot uk
- Date: Mon, 16 May 2005 14:22:06 +0100
- Subject: Re: GCC 4.1: Buildable on GHz machines only?
- References: <17009.2368.986169.753001@cuddles.cambridge.redhat.com> <200504281609.j3SG9ZD27524@makai.watson.ibm.com> <20050428164727.GB30649@synopsys.com> <200504281654.j3SGs0D27158@makai.watson.ibm.com> <oracncw0a1.fsf@livre.redhat.lsd.ic.unicamp.br> <20050503220342.GA23969@synopsys.com> <17016.41624.799846.161219@cuddles.cambridge.redhat.com> <20050504134157.GA5261@lucon.org> <20050504160005.GB26103@synopsys.com> <20050504161719.GA7542@lucon.org> <20050504162944.GA28196@synopsys.com> <20050516120625.A70AA9842C@baradas.org> <42888FCF.4000207@adacore.com> <1116246822.13457.22.camel@pc960.cambridge.arm.com> <428895AA.204@adacore.com>
On Mon, 2005-05-16 at 13:44, Robert Dewar wrote:
> Richard Earnshaw wrote:
>
> > Robert, please stop trying to shoot the messenger. The problems are
> > real, and users often cannot 'fix' these problems themselves. Just like
> > they can't 'fix' the compiler bloat themselves.
>
> Right, but again, if developers make bad decisions about
> development environments, it is not clear that gcc should
> be trying to bail them out.
I didn't say it was the developers of the package, I said it was the
folks trying to *build* the package. These are very often different
people in the open-source community. The folks building the package are
restricted in whether or not they can do cross compilation by whether or
not the *developers* have built that facility into their package.
Sadly, 90%[1] of the time they have not.
> Personally, I would rather have
> a gcc generating better code and using more memory, than
> the other way round. Of course, there are limits, and the
> places that gcc uses unreasonable amounts of memory should
> be fixed. But making it a goal to compile in less than 256 megs
> seems dubious in days when any decently configured notebook
> should have at least a gig or memory (mine has 2 gigs).
I find this laughable. Most desktop machines around here have between
512M and 1G. And if I were lucky enough to own a laptop with 2G of
memory I'd want it to be used to avoid having to spin up the disk on a
regular basis, not as squander-resource for compiler developers who were
being too lazy to think through the consequences of their decisions.
Anyway, with all that extra memory I'd rather be running multiple
parallel compilations than one single one that consumed all the RAM,
especially if I had a multi-core processor.
R.
[1] Random number, I've not measured it. But I'd be very surprised if
it were less than this.