e: GCC 3.3 compile speed regression - AN ANSWER

[Nix]

On Thu, 13 Feb 2003, Tim Josling yowled:
> Have you done this with the profiler? The 'parser' includes a lot of back end
> code through function calls. A lot of suprising things happen. For example,
> the output assembler file still gets opened!

Yes, but very little should get written to it; it gets opened merely
because if it didn't get opened, anything that tried to output little
fragments of assembler to it would core dump (such sometimes happens in
the parsing stage, but not very often, thank goodness).

(e.g. the occasional call in varasm.c kicks off an ASM_OUTPUT_LABEL, but
it's been so long since I touched this that I can't remember what it is
that does that.)

> 'parser' should read 'parser/etc' IMHO.

Yes, but `etc' is quite limited; `parser/early-tree-build' perhaps.

> However most of the optimisation is omitted with syntax-only.

Quite so.

-- 
2003-02-01: the day the STS died.