From: Corey Kosak <kosak@cs.cmu.edu>
To: jason@cygnus.com, jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: excessive memory consumption
Date: Sun, 05 Oct 1997 18:08:00 -0000 [thread overview]
Message-ID: <199710060108.SAA00563@cygnus.com> (raw)
The following program still takes nearly 200M of memory to compile,
even with Jason Merrill's October 3 patch.
% gcc -v
Reading specs from /afs/cs/project/cmcl-kosak/patchloco/lib/gcc-lib/alpha-dec-osf3.2/egcs-2.90.11/specs
gcc version egcs-2.90.11 970929 (gcc2-970802 experimental)
% cat crack.cc
#include <vector>
class foo_t {
public:
vector<int> v;
};
class bar_t {
public:
vector<foo_t> bar;
};
int main()
{
bar_t bar;
}
% limit datasize 200M
% g++ -O2 -Wall crack.cc
/bin/ld:
Warning: Linking some objects which contain exception information sections
and some which do not. This may cause fatal runtime exception handling
problems (last obj encountered without exceptions was /afs/cs/project/cmcl-kosak/patchloco/lib/libstdc++.a).
/bin/ld:
Warning: Linking some objects which contain exception information sections
and some which do not. This may cause fatal runtime exception handling
problems (last obj encountered without exceptions was /afs/cs/project/cmcl-kosak/patchloco/lib/libstdc++.a).
% limit datasize 195M
% g++ -O2 -Wall crack.cc
crack.cc: In function `int main()':
crack.cc:16: virtual memory exhausted
next reply other threads:[~1997-10-05 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-05 18:08 Corey Kosak [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-03 17:03 Mike Stump
[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
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=199710060108.SAA00563@cygnus.com \
--to=kosak@cs.cmu.edu \
--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).