This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Memory leaks?
- To: gcc@gcc.gnu.org, tudor.hulubei@data.ecora.com
- Subject: Re: Memory leaks?
- From: Mike Stump <mrs@wrs.com>
- Date: Tue, 31 Aug 1999 15:40:19 -0700 (PDT)
> Date: Tue, 31 Aug 1999 15:30:53 -0400 (EDT)
> From: Tudor Hulubei <tudor.hulubei@data.ecora.com>
> To: gcc@gcc.gnu.org
> I recently tried to compile a C++ library that the company I'm
> working for is developing and failed miserably (when optimizing)
> because of egcs-1.1.2 trying to use more than 670Mb of memory! (I
> added a 0.5Gb swap partition to no avail).
Don't inline. I think you will find the problem goes away. See my
previous postings about this, they culminated in a patch to
function_cannot_inline_p in integrate.c with a max_insns = ...;
line... here are some unique bits to search for:
Thu Jan 7 20:33:19 1999 Mike Stump <mrs@wrs.com>
* integrate.c (function_cannot_inline_p): Don't inline unreasonably
large functions, even if we say `inline'.
If that doesn't work, try and leave out -Wall.