Mail Archives: djgpp/1997/06/05/13:43:37
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> > On my system (p133, 16Mbyte ram,
> > Win95), DJGPP usually spends equal time in CPP and AS than in CC1,
>
> I find this hard to believe, unless your system has awfully non-optimal
> configuration. A typical compile, even on small modules should dwell in
> CC1 much longer than in CPP and AS. I suggest you check your
> configuration (especially how much free DPMI memory does Windows let you
> use) as per section 3.9 of the FAQ.
Here's a report of my DPMI memory (just a dos box, no other task running)
DPMI memory available: 11755 Kb
DPMI swap space available: 1645 Kb
Maybe the problem is, that i'm realy out of disk space, (50 Megs free), and
I usually runs more apps, (e-mail, wintalk), so there are no swap space,
and lack of memory, what means small disk cache under win95... :(
> With a large cache and TMPDIT that points to a RAM drive, most of the I/O
> to temporary files actually boils down to memory moves, and those are
> lightning fast on a Pentium.
What I said, (what i wanted to say...)
> > And if You can access a U..ix version of gcc, than You can check that
the
> > -pipe option speeds up really the compilation.
>
> Did you actually check this? I did, and on many workstations there is no
> visible difference. The reason, again, is that Unix has a well-tuned
> disk cache.
I saw significant speedups on PC based systems (Linux & BSD), whithout
large cache. Of course when I tried it on a SPARC 20 there wasn't visible
diference.
I think we totaly agree, that disk I/O speed is one of the most significant
(if not THE most significant) factor of the compiling times. And this means
more memory You have, than more cache, larger temp ramdrive, and faster
compiling time You get.
Gyorgy Abonyi Jr.
loop AT hu DOT bonus DOT com
- Raw text -