public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/43058] New: [4.5 Regression] var-tracking uses up all virtual memory
Date: Sat, 13 Feb 2010 19:04:00 -0000 [thread overview]
Message-ID: <bug-43058-10053@http.gcc.gnu.org/bugzilla/> (raw)
/usr/lib64/gcc/x86_64-suse-linux/4.5/cc1 -m32 -fpreprocessed xg.i -quiet
-dumpbase xg.c -mtune=generic -march=i586 -auxbase xg -g -O2 -O2 -Wall -version
-fomit-frame-pointer -fmessage-length=0 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -fno-strict-aliasing -o xg.s --param
ggc-min-expand=100 --param ggc-min-heapsize=131072
uses more than 2GB of virtual memory when on a 32bit host (and thus fails
to compile). On a 64bit host we top at >3GB (I need to re-try on a host
with more memory, I'm swapping to death right now).
Related to PR41371, the offender is var-tracking. Without -g we top
at 600MB on the 64bit host.
I suppose we inline all single-call static functions into Init_libxg
which makes it biiiig (and containing lots of calls).
--
Summary: [4.5 Regression] var-tracking uses up all virtual memory
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Keywords: memory-hog
Severity: normal
Priority: P3
Component: rtl-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rguenth at gcc dot gnu dot org
GCC target triplet: i?86-linux
BugsThisDependsOn: 41371
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43058
next reply other threads:[~2010-02-13 19:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 19:04 rguenth at gcc dot gnu dot org [this message]
2010-02-13 19:06 ` [Bug rtl-optimization/43058] " rguenth at gcc dot gnu dot org
2010-02-13 19:13 ` rguenth at gcc dot gnu dot org
2010-02-13 19:25 ` rguenth at gcc dot gnu dot org
2010-02-13 19:38 ` rguenth at gcc dot gnu dot org
2010-02-13 19:57 ` rguenth at gcc dot gnu dot org
2010-02-15 16:57 ` rguenth at gcc dot gnu dot org
2010-02-17 16:57 ` mmitchel at gcc dot gnu dot org
2010-02-19 11:55 ` rguenth at gcc dot gnu dot org
2010-02-24 18:25 ` jakub at gcc dot gnu dot org
2010-03-05 15:19 ` jakub at gcc dot gnu dot org
2010-03-12 12:06 ` rguenth at gcc dot gnu dot org
2010-03-17 10:58 ` jakub at gcc dot gnu dot org
2010-03-17 15:05 ` jakub at gcc dot gnu dot org
2010-03-18 20:15 ` jakub at gcc dot gnu dot org
2010-03-18 20:31 ` jakub at gcc dot gnu dot org
2010-03-23 0:58 ` wilson at gcc dot gnu dot org
2010-03-23 6:49 ` jakub 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-43058-10053@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).