On Tue, Jun 13, 2000 at 10:29:01AM +0100, Nick Hilliard mentioned:
> In most common source sets, after compiling the first few files, virtually
> all of the commonly used headers are cached by the OS, so most of the
> compile time is going to be CPU bound. A good way to see the bottleneck is
> to compile with "-pipe", which stops all of the intermediate file creation
> dreck (which accounts for most of the disk trashing during gcc compiles).
> "top" should in most cases reveal that the CPU is very busy.
I thought that was default for ages now. I remember when I used GCC on
the amiga, they warned "Only use -pipe when you have more than 6MB of
RAM".
Kate
--
"The fool must be beaten with a stick, for an intelligent person
the merest hint is sufficient" -- Zen Master Greg
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
