From: Peter Bergner <bergner@vnet.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR tree-optimization/51513
Date: Mon, 02 May 2016 12:26:00 -0000 [thread overview]
Message-ID: <1462191985.4256.32.camel@vnet.ibm.com> (raw)
In-Reply-To: <CAFiYyc21q1-9+CafyHvLom-5qTmrDGSzYuRcEHpbZsUomMV+sg@mail.gmail.com>
On Mon, 2016-05-02 at 10:49 +0200, Richard Biener wrote:
> Again, the wild jump is not a bug but at most a missed optimization
> (to remove it).
Sorry, came down with a cold and haven't looked into this yet.
I'll do that today.
I agree it's a missed optimization bug. We noticed this with a post
compilation analysis tool that had problems itself with the wild
branch (since fixed) which is why we wanted to fix this.
Peter
prev parent reply other threads:[~2016-05-02 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 23:35 Peter Bergner
2016-04-29 9:56 ` Richard Biener
2016-04-29 12:09 ` Peter Bergner
2016-05-02 8:49 ` Richard Biener
2016-05-02 12:26 ` Peter Bergner [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=1462191985.4256.32.camel@vnet.ibm.com \
--to=bergner@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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: link
Be 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).