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 c/30610] huge memory consumption with -O3 Date: Sat, 27 Jan 2007 16:51:00 -0000 [thread overview] Message-ID: <20070127165113.29324.qmail@sourceware.org> (raw) In-Reply-To: <bug-30610-9200@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2007-01-27 16:51 ------- All time is suck up in PRE: tree PRE : 36.36 (93%) usr 0.40 (95%) sys 36.85 (93%) wall 88918 kB (96%) ggc TOTAL : 39.03 0.42 39.74 92276 kB though it uses only 512MB for me (and 36s) using a release-checking enabled build from 20070113. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dberlin at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30610
next prev parent reply other threads:[~2007-01-27 16:51 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 [this message] 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
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=20070127165113.29324.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).