Date:	Tue, 21 Mar 2000 19:39:51 +0600 (LKT)
From:	Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Sender:	root AT darkstar DOT grendel DOT net
To:	djgpp AT delorie DOT com
Subject:	Re: Compiling with DJGPP.... how can I speed it?
In-Reply-To:	<38D695EF.AD813E97@americasm01.nt.com>
Message-ID:	<Pine.LNX.4.10.10003211934040.1273-100000@darkstar.grendel.net>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 20 Mar 2000, Campbell, Rolf [SKY:1U32:EXCH] wrote:

> Eli Zaretskii wrote:
> 
> > On Sun, 19 Mar 2000, Kalum Somaratna aka Grendel wrote:
> > > So it follows that on a p-166 your 10000 line program would take about 10
> > > secs to compile. a long time indeed.
> > You are kidding, right?  Because 10 seconds is not even enough time to
> > reflect upon the bugs you might have left lurking in the code you're
> > compiling...
> >
> > Large projects take tens of minutes, sometimes hours, to build.  Now
> > *that* is a long time indeed.  Whereas 10 seconds--well, it's just a
> > blink ;-).
> 
> Some of use are spoiled though.  What I usually do is compile, get a list of x
> compiliation errors, fix the first one, then compile again.  I have found that
> in about 10% of cases, the initial error in the code confuses gcc so it 'make
> up' some of the other errors.  This means that I sometimes compile code every
> 10 seconds.  In general, I believe my effort is more valuable than my CPU's,
> so even if there is only a small chance that the errors will dissapear, I
> still recompile.
>     The point being, if my code doesn't compile in < 2 seconds, I look for
> ways to speed it up.  I realize that, beyond some limit, there is nothing I
> can do, and if most of the time is spent in the linker stage, there's not much
> I can do, but 10 seconds is a long time for most of us.

I am one user who is "spoiled" as you mention Rolf, and 10 secs is too
much for people who have got used to doing what you describe, but Eli
suggested using the "-fsyntax-only" switch to speed up compiles in such
long cases.

Since you mention about the compiler becoming confused, I'm sure many
people would have found that a dropped semicolon at the end of a header
file can lead to a whole lot of irrelevant errors in the source files that
include the header file being flagged by the compiler, with no clue to as
where the problem is actually occuring...


Grendel.

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)

- Raw text -