Mail Archives: djgpp/2009/04/03/14:00:03

X-Authentication-Warning: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: compiler error on Windows 2003
Date: Fri, 3 Apr 2009 11:58:03 -0700 (PDT)
Lines: 35
Message-ID: <>
References: <gr208b$ak2$1 AT news DOT onet DOT pl> <e4f0ea22-d009-4aa0-a3bf-630f3c7a8f28 AT a7g2000yqk DOT googlegroups DOT com>
<gr4lrn$751$1 AT news DOT onet DOT pl> <16d44b1b-8acc-48b3-bf49-45b71e423d78 AT r37g2000yqn DOT googlegroups DOT com>
<gr548r$gpd$1 AT news DOT onet DOT pl>
Mime-Version: 1.0
X-Trace: 1238785083 14627 (3 Apr 2009 18:58:03 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Fri, 3 Apr 2009 18:58:03 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info:; posting-host=;
User-Agent: G2/1.0
X-HTTP-UserAgent: Opera/9.64 (Windows NT 6.0; U; en) Presto/2.1.1,gzip(gfe),gzip(gfe)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


On Apr 3, 8:51=A0am, "Tomasz Zbro=BFek" <t DOT zbro DOT  DOT  DOT  AT upos DOT com DOT pl> wrote:
> Rugxulo <rugx DOT  DOT  DOT  AT gmail DOT com> wrote in
> > You could also try temporarily downgrading to G++ 3.4.4 to compile
> > your stuff, which uses lots less memory than the latest 4.3.2.
> I tried with 3.4.4 and result is much better but on compiling biggest *.c=
> file of the project gpp failed with out of memory. Maybe on monday we wil=
> try to divide this file to smaller parts :) I tried with -O0 option (-Wl,=
> reduce-memory-overheads was not needed yet because it did not reach linki=
> phase).

Try -Wa,--reduce-memory-overheads (for GAS, although I doubt that will
help much). Also try not using "-Wall" and see if that lowers memory
any. Don't forget that 3.4.4 G++ is object incompatible with 4.3.2,
though. As for why it needs so much RAM, I guess the blame goes to
templates, genericity, or whatnot. Heck, you could even try 3.3.6 or
3.2.3 if necessary. Or Maybe try once with "gcc -v" and then manually
do what it does (without using the gcc driver) to decrease its
footprint a little.

EDIT: Ah, I forgot about this, maybe this will help most of all
(although I'm not sure those values are truly optimal, I think 0 and
4096 will work even better but much slower)?

--param ggc-min-expand=3D10 --param ggc-min-heapsize=3D8192

N.B. You may have to use a response file if it surpasses 126 bytes
cmdline length:   gcc @my_options.txt myfile.cpp

- Raw text -

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