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] [4.7/4.8 regression] insane PRE memory usage with PIE (translate.i) Date: Tue, 27 Nov 2012 15:51:00 -0000 [thread overview] Message-ID: <bug-55489-4-Ki9sptNl98@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55489-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489 Paolo Bonzini <bonzini at gnu dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work|4.8.0 | Summary|[4.7 regression] insane PRE |[4.7/4.8 regression] insane |memory usage with PIE |PRE memory usage with PIE |(translate.i) |(translate.i) Known to fail| |4.8.0 --- Comment #1 from Paolo Bonzini <bonzini at gnu dot org> 2012-11-27 15:50:44 UTC --- Strictly not a regression, because the underlying bug is present since always. But something between 4.4.6 and 4.7.2 caused memory usage to become much worse. Also, marking it as not-working in 4.8 because the allocation of reg_known_value is wrong: vec_alloc (reg_known_value, maxreg - FIRST_PSEUDO_REGISTER); and that's what causes the bug to be latent: set_reg_known_value becomes a no-op, and get_reg_known_value always returns NULL.
next prev parent reply other threads:[~2012-11-27 15:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-27 14:08 [Bug rtl-optimization/55489] New: [4.7 " bonzini at gnu dot org 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 ` bonzini at gnu dot org [this message] 2012-11-27 20:27 ` [Bug rtl-optimization/55489] [4.7/4.8 " 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-Ki9sptNl98@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).