This is the mail archive of the
mailing list for the GCC project.
Re: Faster compilation speed
- From: Stan Shebs <shebs at apple dot com>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Mike Stump <mrs at apple dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 09 Aug 2002 15:42:25 -0700
- Subject: Re: Faster compilation speed
- References: <200208092203.SAA24908@makai.watson.ibm.com>
David Edelsohn wrote:
Stan> I think it suffices to have -O0 mean "go as fast as possible". From time to
Stan Shebs writes:
Stan> time, I've noticed that there's been a temptation to try to sneak in a
Stan> optimization even at -O0, presumably with the assumption that the time
Stan> penalty was negligible. (There are users who complain that -O0 should
Stan> do some amount of optimization, but IMHO we should ignore them.)
Saying "do not run any optimization at -O0" shows a tremendous
lack of understanding or investigation.
Shoot, then I guess I need to go back and ask for a refund from the
diploma mill. :-)
One wants minimal optimization
even at -O0 to decrease the size of the IL representation of the function
being compiled. The little bit of computation to perform trivial
optimization more than makes up for itself with the decreased size of the
IL that needs to be processed to generate the output.
Well duh. But if people were really keeping that more in mind,
then I would expect to see patches come with a "yes this adds
to expression expansion time, but it pays for itself in reload"