public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tudor Hulubei <tudor@cs.unh.edu>
To: egcs@cygnus.com
Cc: "Jeffrey A. Law" <law@schirf.cs.utah.edu>,
	Jason Merrill <jason@cygnus.com>,
	Fred Richardson <frichard@bbn.com>
Subject: Re: Patch for memory blowup
Date: Thu, 11 Dec 1997 23:55:00 -0000	[thread overview]
Message-ID: <199712120900.EAA29971@hal.ttlc.net> (raw)
In-Reply-To: <199712120113.RAA26139@supernova.earthlink.net>

Hi,

 > I believe I have a patch (attached) for the memory explosions that
 > occur when using g++ -O2 -Wall with lots of templates.  See for
 > example:

I applied the patch (by hand) to egcs-1.0 and indeed, it made a big
difference.  gcc previously required around 150-170Mb to compile it,
now we're down to 69Mb.  And the generated code works fine.  Thanks.

Tudor

  parent reply	other threads:[~1997-12-11 23:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-11 17:11 Mark Mitchell
1997-12-11 22:59 ` Mark Mitchell
1997-12-15 10:37   ` Jeffrey A Law
1997-12-11 23:55 ` Tudor Hulubei [this message]
1997-12-12  7:40 ` Bruce Korb
1997-12-12  7:49   ` Jeffrey A Law
1997-12-12 10:18   ` Mark Mitchell
1997-12-12 17:52 Peter Schmid

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=199712120900.EAA29971@hal.ttlc.net \
    --to=tudor@cs.unh.edu \
    --cc=egcs@cygnus.com \
    --cc=frichard@bbn.com \
    --cc=jason@cygnus.com \
    --cc=law@schirf.cs.utah.edu \
    /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).