public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Peter van Hoof <p.van-hoof@qub.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10155: [3.3/3.4 regression] gcc -O2/-O3 uses excessive amount of memory
Date: Tue, 06 May 2003 20:46:00 -0000	[thread overview]
Message-ID: <20030506204602.30583.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10155; it has been noted by GNATS.

From: Peter van Hoof <p.van-hoof@qub.ac.uk>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, jh@suse.de, 
    rakdver@atrey.karlin.mff.cuni.cz
Subject: Re: optimization/10155: [3.3/3.4 regression] gcc -O2/-O3 uses excessive
         amount of memory
Date: Tue, 06 May 2003 21:41:00 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10155
 
 
 > It looks like it's related to the amount of RAM in your
 > box.  For me, GCC -O2 never consumes more than 40MB, and
 > my machine has 192MB.  If your system pulls it off to
 > keep cc1 alive up to 1772MB, then I suppose you have at
 > least four times as much, so your GC param settings will
 > be much larger than mine --> GCC eats more memory.  That
 > _should_ give you a nice speedup over older GCC 3.x...
 > So perhaps we can change the synopsis to reflect that his
 > really only is a bug with -O3.
 > 
 > Peter, if you compile with "gcc -v", you can see your
 > garbage collector parameter settings.  For me they are:
 > GGC heuristics: --param ggc-min-expand=42 --param ggc-min-heapsize=23891
 > 
 > Can you show us your settings?
 
 Now that my computer is back in the land of the living, I can finally answer 
 this (in case it is still relevant)... I ran the initial test case on a Sun 
 Blade 100 with 2GB of RAM, these are the settings with this machine:
 
 GNU C version 3.4 20030504 (experimental) (sparc-sun-solaris2.9)
 	compiled by GNU C version 3.4 20030504 (experimental).
 GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
 
 The compiler reaches a maximum size of 1894MB, which means that the machine has 
 to swap out some other processes. I also have an Ultra 5 with 640MB of RAM, 
 these are the settings on that machine
 
 GGC heuristics: --param ggc-min-expand=73 --param ggc-min-heapsize=81920
 
 I killed the compilation when the compiler grew to >1700MB because swap space 
 was running dangerously low, i.e. on this machine the compiler would use up all 
 the swap space it could get its hands on.
 
 
 Hope this helps...
 
 Peter.
 


             reply	other threads:[~2003-05-06 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 20:46 Peter van Hoof [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02 19:16 Zdenek Dvorak
2003-05-02 17:46 Zdenek Dvorak
2003-05-02 13:26 Jan Hubicka
2003-05-02 11:06 Steven Bosscher
2003-04-15  8:51 ebotcazou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030506204602.30583.qmail@sources.redhat.com \
    --to=p.van-hoof@qub.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).