From: Max Lawson <mlawson@drfmc.ceng.cea.fr>
To: egcs@cygnus.com, law@cygnus.com, jason@cygnus.com
Subject: Re: Continued: egcs-971201: testsuite results for i586-pc-linux-gnulibc1
Date: Wed, 03 Dec 1997 05:46:00 -0000 [thread overview]
Message-ID: <9712031346.AA10496@drfmc.ceng.cea.fr> (raw)
> From jason@cygnus.com Wed Dec 3 03:09 MET 1997
>
> >>>>> Max Lawson <mlawson@drfmc.ceng.cea.fr> writes:
>
> > $g++ -Wall -O test.cc
> > test.cc: In function `int main()':
> > test.cc:10: virtual memory exhausted
>
> As I said before, you need to add -Wno-return-type or the old memory
> explosion bug resurfaces. This is a known bug. The problem is that
> save_for_inline_copying wastes a ridiculous amount of memory in the
> presence of recursive function definitions, which you get with templates.
> With -Wno-return-type, we don't need to use save_for_inline_copying.
I do not need to use any warning flag to obtain memory explosion. The
-Wno-return-type flag indeed solve the posted testcase problem, but can't
help.
I am now aware that my problem is mentioned in the first part of the online
faq (subject: virtual memory error). But what's called a large file ? And
how to simplify files ? In order to use template one has to merge header and
source files ....
Thanx for the answers, Max.
next reply other threads:[~1997-12-03 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-03 5:46 Max Lawson [this message]
1997-12-03 12:54 ` Jason Merrill
[not found] <9712021644.AA20857.cygnus.egcs@drfmc.ceng.cea.fr>
1997-12-02 20:32 ` Jason Merrill
1997-12-02 18:13 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 9:56 Max Lawson
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=9712031346.AA10496@drfmc.ceng.cea.fr \
--to=mlawson@drfmc.ceng.cea.fr \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=law@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).