delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/11/04/22:51:47

Date: Wed, 05 Nov 1997 16:54:12 +1100
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: FYI: speed of Allegro/DJGPP
In-reply-to: <Pine.SUN.3.91.971103103246.14641K-100000@is>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Message-id: <199711050351.QAA23074@teleng1.tait.co.nz gatekeeper.tait.co.nz>
Organization: Tait Electronics Limited
MIME-version: 1.0
References: <199711022157 DOT KAA13126 AT teleng1 DOT tait DOT co DOT nz gatekeeper.tait.co.nz>
Comments: Authenticated sender is <billc AT blackmagic DOT tait DOT co DOT nz>

On  3 Nov 97 at 10:33, Eli Zaretskii wrote:

> 600K for TMPDIR is only enough for *very* short sources.  When the

Eh? Depends on your idea of short. I don't routinely compile GNU 
sources on my 386, so very short to me is <1k with no headers.

> RAM drive fills, gcc aborts very ungracefully, and with error
> messages that don't always make sense (sometimes it says ``virtual
> memory exhausted'', sometimes just ``Abort!'', sometimes it
> SIGSEGVs.  Such a small TMPDIR requires a lot of vigilance.

Yes, but I don't normally work with programs so big they generate 
600k temp files. anyway, if I need the space, I just zap the unused 
compiler.

> People seldom use both cc1 and cc1plus at the same time.

True, but I was grouping them. cc1plus uncompressed is 1.6M (? can't 
remeber, I compressed it a while ago) and even a 12M machine pages, 
so the cache gets filled with cc1plus and virtual memory, not much 
use to me when I can wind up pulling in a dozen headers repeatedly.

However, I agree with you totaly that my setup is not for the faint 
of heart. It does often require fine tuning.

Bill
--
Leave others their otherness.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019