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/60577] [4.7/4.8 Regression] inefficient FDO instrumentation code Date: Fri, 21 Mar 2014 11:53:00 -0000 [thread overview] Message-ID: <bug-60577-4-ZzwlMLH4FE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60577-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60577 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.9.0 Summary|[4.7/4.8/4.9 Regression] |[4.7/4.8 Regression] |inefficient FDO |inefficient FDO |instrumentation code |instrumentation code --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed on trunk.
next prev parent reply other threads:[~2014-03-21 11:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-19 3:02 [Bug tree-optimization/60577] New: " carrot at google dot com 2014-03-19 10:02 ` [Bug tree-optimization/60577] [4.9 Regression] " rguenth at gcc dot gnu.org 2014-03-19 10:54 ` [Bug tree-optimization/60577] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org 2014-03-19 11:51 ` rguenth at gcc dot gnu.org 2014-03-19 12:04 ` rguenth at gcc dot gnu.org 2014-03-19 12:36 ` rguenth at gcc dot gnu.org 2014-03-20 11:36 ` rguenth at gcc dot gnu.org 2014-03-21 11:53 ` rguenth at gcc dot gnu.org [this message] 2014-03-21 11:53 ` [Bug tree-optimization/60577] [4.7/4.8 " rguenth at gcc dot gnu.org 2014-04-22 11:38 ` jakub at gcc dot gnu.org 2014-07-16 13:31 ` [Bug tree-optimization/60577] [4.8 " jakub at gcc dot gnu.org 2014-10-30 10:43 ` jakub at gcc dot gnu.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-60577-4-ZzwlMLH4FE@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).