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 tree-optimization/32723] [4.2 Regression] memory hog in solve_graph Date: Mon, 16 Jul 2007 09:12:00 -0000 [thread overview] Message-ID: <20070716091220.9747.qmail@sourceware.org> (raw) In-Reply-To: <bug-32723-14802@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2007-07-16 09:12 ------- /tmp> ~/bin/maxmem2.sh gcc-4.1 -S -O2 -o /dev/null fail.c total: 96228 kB /tmp> ~/bin/maxmem2.sh gcc-4.2 -S -O2 -o /dev/null fail.c total: 1579668 kB trunk: /tmp> ~/bin/maxmem2.sh /space/rguenther/tramp3d/install/bin/gcc -S -O2 -o /dev/null fail.c total: 109731 kB meh. Danny, do you remember which change on the trunk could have improved this? Maybe http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122741? -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dberlin at gcc dot gnu dot | |org, rguenth at gcc dot gnu | |dot org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-07-16 09:12:19 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32723
next prev parent reply other threads:[~2007-07-16 9:12 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-10 18:11 [Bug tree-optimization/32723] New: " pixel at mandriva dot com 2007-07-10 18:16 ` [Bug tree-optimization/32723] " pixel at mandriva dot com 2007-07-10 20:23 ` pinskia at gcc dot gnu dot org 2007-07-10 22:21 ` pixel at mandriva dot com 2007-07-11 10:23 ` pixel at mandriva dot com 2007-07-15 20:51 ` pinskia at gcc dot gnu dot org 2007-07-16 9:12 ` rguenth at gcc dot gnu dot org [this message] 2007-07-16 9:28 ` rguenth at gcc dot gnu dot org 2007-07-20 3:49 ` mmitchel at gcc dot gnu dot org 2007-07-24 7:16 ` dberlin at gcc dot gnu dot org 2007-07-24 7:31 ` rguenth at gcc dot gnu dot org 2007-07-24 7:31 ` rguenth at gcc dot gnu dot org 2007-08-11 17:08 ` pixel at mandriva dot com 2007-08-20 1:56 ` dberlin at gcc dot gnu dot org 2007-08-21 13:29 ` pixel at mandriva dot com 2007-09-05 0:58 ` mmitchel at gcc dot gnu dot org 2007-10-09 19:27 ` mmitchel at gcc dot gnu dot org 2007-10-31 13:08 ` rguenth at gcc dot gnu dot org 2007-10-31 14:22 ` dberlin at dberlin dot org 2008-02-01 17:04 ` jsm28 at gcc dot gnu dot org 2008-03-16 17:30 ` rguenth at gcc dot gnu dot org 2008-03-16 17:33 ` rguenth 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=20070716091220.9747.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).