public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29948] G++ OOM's when compiling kmail
Date: Sat, 22 Oct 2011 11:50:00 -0000 [thread overview]
Message-ID: <bug-29948-4-m7Ppqyy9eb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29948-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29948
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution| |WORKSFORME
--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-10-22 11:49:48 UTC ---
4.1 is just too old, and this issue is too vague to be able to identify if
there is a problem at all, or g++ just needs that amount of memory. Sorry, I am
closing this. If you can isolate a single file that makes g++ suddenly
increase memory without apparent limit, you may try generating a reduced
preprocessed testcase: http://gcc.gnu.org/bugs/#need and reopen this.
next parent reply other threads:[~2011-10-22 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29948-4@http.gcc.gnu.org/bugzilla/>
2011-10-22 11:50 ` manu at gcc dot gnu.org [this message]
2006-11-22 22:20 [Bug c++/29948] New: " sjoerd-gcc at linuxonly dot nl
2006-11-22 22:24 ` [Bug c++/29948] " pinskia at gcc dot gnu dot org
2006-11-22 22:27 ` sjoerd-gcc at linuxonly dot nl
2007-01-29 21:59 ` n dot escuder at intra-links dot com
2007-02-05 21:12 ` sliedes at cc dot hut dot fi
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=bug-29948-4-m7Ppqyy9eb@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).