Date:	Fri, 3 Apr 92 09:45:22 EST
From:	DJ Delorie <dj AT ctron DOT com>
To:	APM233M AT vaxc DOT cc DOT monash DOT edu DOT au
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	1.06: cc1 memory hungry, gcc slow
Status:	O

>I tried a compilation of a simple "C" file. Two of the modules involved in
>the compilation did some swapping to disk (I assume that these are gcc.exe
>and cc1.exe). The simple compilation took a grinding 57 sec to complete.

Same thing happens on my SparcStation when I start paging.

>Can cc1.exe be modified to be less memory hungry?

Not really; I used the -O switch to make it as small as possible.

>gcc.exe (the control program which just spawns the pre-processor, compiler,
>etc) which was (I think) a "Turbo C" program is now a "DJGPP" program. Thus
>a program which once just sat in memory now swaps out and in several times
>during a compilation. I believe that this does not save much memory since
>there will now be two copies of go32 in memory most of the time.

It is a djgpp program because it's easier to port that way, and
Richard Stallman wanted it that way.

>I tried returning to the 1.05 version of gcc.exe (leaving all of the other
>1.06 versions of the compiler modules installed) and the simple compilation
>now takes about 25 seconds! There appear to be only minor differences between
>the two versions of gcc.exe. Can I continue to use the 1.05 version, or do
>other parts of DJGPP now need the new parameters passed by the 1.06 gcc.exe?

You really do need the 1.06 version of gcc, as it passes new switches to
the passes.

>(Oh yes, one other minor side-effect of v1.06 was that I had to change the
>definition of TMP in "autoexec.bat" from "SET TMP=F:\TMP" to "SET TMP=F:/TMP".
>Other programs use TMP, so I am keeping my fingers crossed and hoping that
>they will not barf at the change.)

Interesting.  I'll have to investigate this.

DJ
dj AT ctron DOT com
Life is a banana.

- Raw text -