public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55489] New: [4.7 regression] insane PRE memory usage with PIE (translate.i) Date: Tue, 27 Nov 2012 14:08:00 -0000 [thread overview] Message-ID: <bug-55489-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489 Bug #: 55489 Summary: [4.7 regression] insane PRE memory usage with PIE (translate.i) Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Keywords: memory-hog Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: bonzini@gnu.org Created attachment 28793 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28793 gzipped preprocessed source Yet another evil testcase, this time for RTL GCSE. Compile with: $ gcc ~/translate.i -g -O2 -fPIE gcc 4.4.6: PRE : 3.83 (24%) usr 0.15 (17%) sys 3.99 (24%) wall 267307 kB (33%) ggc gcc 4.7.2: PRE : 7.95 (41%) usr 0.40 (40%) sys 8.31 (41%) wall 821017 kB (80%) ggc Fixed, or latent in trunk: gcc 4.8.0: PRE : 6.94 (26%) usr 0.02 ( 4%) sys 6.98 (26%) wall 731 kB ( 0%) ggc
next reply other threads:[~2012-11-27 14:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-27 14:08 bonzini at gnu dot org [this message] 2012-11-27 14:09 ` [Bug rtl-optimization/55489] " bonzini at gnu dot org 2012-11-27 14:20 ` rguenth at gcc dot gnu.org 2012-11-27 15:51 ` [Bug rtl-optimization/55489] [4.7/4.8 " bonzini at gnu dot org 2012-11-27 20:27 ` bonzini at gnu dot org 2012-11-27 20:29 ` bonzini at gnu dot org 2012-11-28 9:30 ` bonzini at 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-55489-4@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: 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).