public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: jason@cygnus.com (Jason Merrill)
Cc: jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: excessive memory consumption
Date: Fri, 03 Oct 1997 15:44:00 -0000	[thread overview]
Message-ID: <199710032243.PAA03921@atrus.synopsys.com> (raw)
In-Reply-To: <u9oh56zn5s.fsf@yorick.cygnus.com>

Jason writes:
> Found it!  In situations of recursive instantiation, there can be a lot of
> stuff compiled in the middle of compiling a given function, running up the
> label count.  save_for_inline_copying creates new labels for everything
> between min_labelno and max_labelno, which can add up to a *lot* of space.

Congratulations!  With your patch, that last case I posted takes about the
same virtual memory whether templates are used or not.  That is, about 30
meg instead of 490 meg.

If we still had a support contract, I'd say you could close the call. :-)

  reply	other threads:[~1997-10-03 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199709300033.RAA17703.cygnus.egcs@atrus.synopsys.com>
1997-10-03 12:01 ` Jason Merrill
1997-10-03 15:44   ` Joe Buck [this message]
1997-10-04 13:54   ` Manfred Hollstein
1997-10-05 11:07     ` Manfred Hollstein
1997-10-05 18:08 Corey Kosak
  -- strict thread matches above, loose matches on Subject: below --
1997-10-03 17:03 Mike Stump
1997-09-29 17:33 Joe Buck
1997-09-29 19:14 ` Joe Buck
1997-09-29 20:22   ` Ross Alexander
1997-09-30  5:52 ` Jan Springer
1997-09-30  6:01   ` Jan Springer
1997-10-06  8:29     ` Jan Springer

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=199710032243.PAA03921@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=jason@cygnus.com \
    /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).