Date: Mon, 2 Mar 1998 09:49:51 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill Bouma <bouma AT geoplex DOT com>
cc: "'A. Sinan Unur'" <sinan DOT unur AT cornell DOT edu>, djgpp AT delorie DOT com
Subject: Re: gcc running out of memory?
In-Reply-To: <34F9F6B5.26CF4931@geoplex.com>
Message-ID: <Pine.SUN.3.91.980302094920.15685G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 1 Mar 1998, Bill Bouma wrote:

> So I upped the stack size of "cc1plus" to 4MB and the compilation worked!

I suggest to experiment with lowering the stack size.  4MB should not
be needed except in extremely rare cases.  1MB or 1.5MB should be
enough.  The disadvantage of specifying a stack which is too large is
that it is allocated at startup and wastes memory when it is not used.

> So this brings up the question, is cc1plus doing its own preprocessing
> of the file and not using cpp?  "gcc -v" doesn't show cpp being called.

As "gcc -v" shows, `cpp' *is* used for preprocessing.  The problem is
most probably not with the macros themselves, but with the code that
they expand into.  Try to preprocess the source by running `cpp', and
then compile the expanded source and see if you see any difference.
I'd guess that cc1plus will do the same (i.e., gobble a lot of stack
space) with the pre-processed source as well.