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] [4.5 Regression] var-tracking uses up all virtual memory Date: Fri, 19 Feb 2010 11:55:00 -0000 [thread overview] Message-ID: <20100219115529.31120.qmail@sourceware.org> (raw) In-Reply-To: <bug-43058-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from rguenth at gcc dot gnu dot org 2010-02-19 11:55 ------- The recent patch to add PARAM_MAX_VARTRACK_SIZE didn't fix this. We still top out beyond what my machine with 3GB ram and 1GB swap can handle. GCC 4.4.3 tops at 620MB GCC 4.5 with -fno-var-tracking-assignments tops at 610MB, same with -fno-var-tracking Honza, if we implement partial inlining, can we implement function splitting? :) -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu dot | |org, jakub at gcc dot gnu | |dot org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-02-19 11:55:28 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43058
next prev parent reply other threads:[~2010-02-19 11:55 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-13 19:04 [Bug rtl-optimization/43058] New: " rguenth at gcc dot gnu dot org 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 [this message] 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=20100219115529.31120.qmail@sourceware.org \ --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: linkBe 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).