This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Suggestion for option
- To: mark at codesourcery dot com (Mark Mitchell)
- Subject: Re: Suggestion for option
- From: Joern Rennecke <amylaar at redhat dot com>
- Date: Thu, 26 Jul 2001 23:08:56 +0100 (BST)
- Cc: amylaar at redhat dot com (Joern Rennecke),rjvbertin at hotmail dot com (RenE J.V. Bertin),gcc at gcc dot gnu dot org (gcc at gcc dot gnu dot org)
> Your hapless computer does not go on to the next file and start compiling
> that while it is sitting there waiting for this one to finish. And
> yes, I have seen GCC spend half an hour optimizing a file that it issued
> an error message about. And if you can use parallel make, which you can't
P.S.: It can actually be an advantage when the compiler mulls a bit over
your code after issuing an error. If it suddenly accelerates parsing after
having found a syntax error, you might end up with several thousand error
messages almost instantly, so before you have a chance to press ctrl-c,
all the salient information has already scrolled away. And if you are
compiling remotely over a moderately fast link, you might see your TCP
connection degrade to rather high latencies.