From: Jakub Jelinek <jakub@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, dje.gcc@gmail.com,
wschmidt@linux.vnet.ibm.com
Subject: Re: Backports to 6 (and 7, and 5)
Date: Tue, 27 Jun 2017 17:36:00 -0000 [thread overview]
Message-ID: <20170627173555.GV2123@tucnak> (raw)
In-Reply-To: <20170627160237.GB16550@gate.crashing.org>
On Tue, Jun 27, 2017 at 11:02:37AM -0500, Segher Boessenkool wrote:
> On Tue, Jun 27, 2017 at 09:18:07AM +0200, Richard Biener wrote:
> > On Mon, 26 Jun 2017, Segher Boessenkool wrote:
> > > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg01853.html
> > > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg01923.html
> > > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02048.html
> > > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02606.html
> > > bb-reorder: Improve compgotos pass (PR71785)
> >
> > It's not clear this fixes a regression and as it is
> > a missed-optimization I'd not backport it at this point in time
> > (I understand it's in GCC 7 already).
>
> It's a regression from 3.x, and a pretty severe one, but we can live
> with it for a bit longer, it's a bit invasive for a backport.
It is just a missed-optimizations, not wrong-code, and the regression is
pretty old, so I think it doesn't hurt it if it stays fixed only in 7+.
Jakub
prev parent reply other threads:[~2017-06-27 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 22:31 Segher Boessenkool
2017-06-27 7:18 ` Richard Biener
2017-06-27 16:02 ` Segher Boessenkool
2017-06-27 17:36 ` Jakub Jelinek [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=20170627173555.GV2123@tucnak \
--to=jakub@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.vnet.ibm.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).