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/56522] [4.8 Regression] Bytemark ASSIGNMENT 9% / 11% slower Date: Tue, 05 Mar 2013 10:05:00 -0000 [thread overview] Message-ID: <bug-56522-4-KbpTy8MeXi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56522-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56522 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org Target Milestone|--- |4.8.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> 2013-03-05 10:04:11 UTC --- Can you create a testcase that pinpoints the different forwprop results?
next prev parent reply other threads:[~2013-03-05 10:05 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-04 15:41 [Bug tree-optimization/56522] New: " wbrana at gmail dot com 2013-03-05 10:05 ` rguenth at gcc dot gnu.org [this message] 2013-03-05 12:53 ` [Bug tree-optimization/56522] " rguenth at gcc dot gnu.org 2013-03-06 15:07 ` jakub at gcc dot gnu.org 2013-03-07 8:33 ` rguenther at suse dot de 2013-03-07 18:35 ` wbrana at gmail dot com 2013-03-08 14:19 ` wbrana at gmail dot com 2013-03-08 14:23 ` wbrana at gmail dot com 2013-03-08 14:24 ` wbrana at gmail dot com 2013-03-08 14:25 ` wbrana at gmail dot com 2013-03-08 15:29 ` rguenth at gcc dot gnu.org 2013-03-08 17:28 ` wbrana at gmail dot com 2013-03-08 17:36 ` wbrana at gmail dot com 2013-03-08 17:41 ` wbrana at gmail dot com 2013-03-08 17:58 ` wbrana at gmail dot com 2013-03-11 8:45 ` rguenth at gcc dot gnu.org 2013-03-12 14:29 ` wbrana at gmail dot com 2013-03-12 14:34 ` rguenther at suse dot de 2013-03-20 11:37 ` [Bug tree-optimization/56522] [4.8/4.9 " wbrana at gmail dot com
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-56522-4-KbpTy8MeXi@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).