public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/44688] [4.6/4.7/4.8 Regression] Excessive code-size growth at -O3 Date: Tue, 11 Dec 2012 10:26:00 -0000 [thread overview] Message-ID: <bug-44688-4-DOsdeSpZWu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44688-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44688 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Known to work| |4.8.0 Resolution| |FIXED Target Milestone|4.6.4 |4.8.0 Known to fail| |4.6.4, 4.7.2 --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-11 10:26:30 UTC --- The original reason for this bug, compile-time and code-size growth of SPEC CPU 2006 and Polyhedron on AMD Barcelona with -march=native has been fixed (back to levels before the -fprefetch-loop-arrays defaulting). For 4.8, that is. Backporting not really possible (requires preserving of loop structure), thus wontfix on the branches.
prev parent reply other threads:[~2012-12-11 10:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44688-4@http.gcc.gnu.org/bugzilla/> 2011-01-19 15:49 ` [Bug tree-optimization/44688] [4.6 " rguenth at gcc dot gnu.org 2011-03-25 21:33 ` [Bug tree-optimization/44688] [4.6/4.7 " jakub at gcc dot gnu.org 2011-06-27 16:12 ` jakub at gcc dot gnu.org 2011-10-26 17:49 ` jakub at gcc dot gnu.org 2012-02-22 10:13 ` rguenth at gcc dot gnu.org 2012-03-01 15:09 ` jakub at gcc dot gnu.org 2012-04-18 11:36 ` [Bug tree-optimization/44688] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2012-04-19 8:53 ` rguenth at gcc dot gnu.org 2012-04-19 8:58 ` rguenth at gcc dot gnu.org 2012-04-19 9:07 ` rguenth at gcc dot gnu.org 2012-12-11 10:26 ` rguenth at gcc dot gnu.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=bug-44688-4-DOsdeSpZWu@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).