Mail Archives: djgpp-announce/1993/07/01/19:09:36
Date: Thu, 1 Jul 93 11:10:50 -0400
From: rth AT sparta DOT com (Robert T. Harris)
Message-Id: <9307011510 DOT AA06672 AT sparta DOT com>
To: djgpp-announce AT sun DOT soe DOT clarkson DOT edu
Subject: Compile Speed Problems?
Status: R
I just started fiddling with the DJGPP version 110 software and have a
problem compiling almost any program within a reasonable amount of time.
I have the software loaded on a 386DX-25MHZ machine with 8 Megs of physical
memory using ST-277-1 (28ms) disk drives. Even compiling main(void){}
resulted in 3 minute compiles. I let the compiler thrash on the sample
programs (3 hour compiles) last night. I tried with QEMM386 and with
HIMEM.SYS (using extended memory) with the same results. I have previously
used the GCC compiler under the linux operating system with normal results
(i.e compiles within seconds) and of course Borland C++. I am sending this
message not to complain but to ask - what have I missed? Is the DJGPP really
this slow? I have set up the tmp file on drive C: while the compiler and
source code reside on drive D: - looking at the lights on the drives it
appears that significant paging is occuring. I am using Stacker 3.0 on
both drives C and D - any clues?
Bob Harris
DJGCC should not be this slow.
Check to make sure that you have PLENTY of conventional RAM before you
compile. Run 'mem' right before you compile, and see what it gives
you. Your make program may be using a lot of memory. I used to use
Borland 3.1 make, and experienced very slow compile times. Then I
cleaned up my autoexec.bat and switched to dmake. Compile times
improved significantly.
Erik R Johnson erik AT microware DOT com
- Raw text -