This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Faster compilation speed
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Matt Austern <austern at apple dot com>
- Cc: Alan Lehotsky <apl at alum dot mit dot edu>, David Edelsohn <dje at watson dot ibm dot com>, Stan Shebs <shebs at apple dot com>, Mike Stump <mrs at apple dot com>, gcc at gcc dot gnu dot org
- Date: 10 Aug 2002 11:21:46 +0200
- Subject: Re: Faster compilation speed
- Organization: CodeSourcery, LLC
- References: <B7FD0B40-ABF2-11D6-A76D-000393B2ABA2@apple.com>
Matt Austern <austern@apple.com> writes:
| On Friday, August 9, 2002, at 04:17 PM, Alan Lehotsky wrote:
|
| > This is DEFINITELY TRUE!
| >
| > For example, the Bliss11 compiler ACTUALLY ran faster with
| > optimization turned on because assembling the unoptimized code
| > actually took longer than the time running FULL optimization required
| > for anything but the most trivial programs.
|
| Shall we take it as a given that nobody is going to check
| in a patch for faster compilations without benchmarking
| and making sure that it really does speed things up?
Some while ago, when the compiler slowdown was a hotter issue, it was
suggested that no new optimization-related patches should be checked
in if there were no concrete evidence that they're bringing noticeable
wins. I don't know how that turns out, though.
-- Gaby