From: Manfred Hollstein <manfred@s-direktnet.de>
To: jason@cygnus.com, jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: excessive memory consumption
Date: Sun, 05 Oct 1997 11:07:00 -0000 [thread overview]
Message-ID: <199710051806.UAA16455@saturn.s-direktnet.de> (raw)
In-Reply-To: <199710042053.WAA00236@saturn.s-direktnet.de>
On Sat, 4 October 1997, 22:53:05, manfred@s-direktnet.de wrote:
On , 3 October 1997, 12:01:19, jason@cygnus.com wrote:
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.
Well, sounds great, but unfortunately, it doesn't work completely; I'm
getting unresolved symbols from libstdc++.so (vtables for __case_table
or so - sorry, removed the logfile too early) on i586-linux-gnulibc1.
Without your patch to toplev.c everything is ok. Looks like we have to
look further :-(
The patch just posted by Alexandre Oliva (Missing virtual tables for
type_info classes in tinfo.cc) cured this problem.
Manfred.
next prev parent reply other threads:[~1997-10-05 11:07 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
1997-10-04 13:54 ` Manfred Hollstein
1997-10-05 11:07 ` Manfred Hollstein [this message]
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=199710051806.UAA16455@saturn.s-direktnet.de \
--to=manfred@s-direktnet.de \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=jbuck@synopsys.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).