public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gasper.azman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/29442] insn-attrtab has grown too large
Date: Wed, 02 May 2012 16:29:00 -0000 [thread overview]
Message-ID: <bug-29442-4-XP810O5aya@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29442-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29442
Gašper Ažman <gasper.azman at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gasper.azman at gmail dot
| |com
--- Comment #11 from Gašper Ažman <gasper.azman at gmail dot com> 2012-05-02 16:28:52 UTC ---
I can confirm this is still a problem on 2.5.3. Compiling on a system with
256MB memory (hired, remote, virtualized) is not possible without an extra 1GB
of memory and almost nothing else running (the memory usage peaked at full RAM
and 522MB swap used, with gcc using everything but 60MB).
next parent reply other threads:[~2012-05-02 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29442-4@http.gcc.gnu.org/bugzilla/>
2012-05-02 16:29 ` gasper.azman at gmail dot com [this message]
2012-05-02 16:53 ` manu at gcc dot gnu.org
2012-05-04 20:05 ` steven at gcc dot gnu.org
2012-05-04 20:19 ` steven at gcc dot gnu.org
2012-05-07 0:19 ` steven at gcc dot gnu.org
2012-05-07 7:55 ` jakub at gcc dot gnu.org
2012-05-07 8:35 ` jakub at gcc dot gnu.org
2012-05-07 12:29 ` matz at gcc dot gnu.org
2012-05-07 12:38 ` jakub at gcc dot gnu.org
2006-10-12 16:11 [Bug other/29442] New: " rick at hartmantech dot com
2006-10-14 3:39 ` [Bug other/29442] " pinskia at gcc dot gnu dot org
2006-10-14 4:16 ` vapier at gentoo dot org
2006-10-25 12:44 ` JoeGTN1 at NetZero dot net
2006-10-25 16:23 ` rick at hartmantech dot com
2007-07-23 5:53 ` konig12 at gmail dot com
2007-10-27 12:47 ` rask at gcc dot gnu dot org
2007-10-28 12:40 ` rask at gcc dot gnu dot org
2007-10-28 12:57 ` rask at gcc dot gnu dot org
2007-10-28 17:48 ` rask at gcc dot gnu dot org
2009-02-22 14:19 ` steven at gcc dot gnu dot org
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-29442-4-XP810O5aya@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).