Precompiled headers (or other speed ups)

[dewar@gnat.com]

<<  Well, only really surprising if you assume the parsing code is well
written :-) After all, the mid/backend is mostly doing memory-memory
transforms on the trees, and that's going to run as fast as your cache
and cpu can handle.  Parsers, OTOH, have to I/O.  Badly written parsers
might even use c stdio functions to fgetc the entire file one char at a
time....
>>

Sure, but that presumably is an easy thing to fix. In GNAT, the entire
file is read with a single read, and then all access to the file is to
the in memory copy, which stays around throughout the compilation.