public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kcwu at csie dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/30610] huge memory consumption with -O3 Date: Sat, 23 Feb 2008 16:22:00 -0000 [thread overview] Message-ID: <20080223162158.21433.qmail@sourceware.org> (raw) In-Reply-To: <bug-30610-9200@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from kcwu at csie dot org 2008-02-23 16:21 ------- this issue is resolved in gcc 4.3 20080221 snapshot. $ time gcc43 -O3 -c f5.c -Wall user 0m0.418s And the memory usage is less than 10 MB. -- kcwu at csie dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30610
prev parent reply other threads:[~2008-02-23 16:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-27 16:25 [Bug c/30610] New: " kcwu at csie dot org 2007-01-27 16:26 ` [Bug c/30610] " kcwu at csie dot org 2007-01-27 16:51 ` rguenth at gcc dot gnu dot org 2007-01-27 17:07 ` rguenth at gcc dot gnu dot org 2007-08-13 12:06 ` [Bug middle-end/30610] " dberlin at gcc dot gnu dot org 2008-02-23 16:22 ` kcwu at csie dot org [this message]
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=20080223162158.21433.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).