From: Richard Biener <rguenther@suse.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, jakub@redhat.com, dje.gcc@gmail.com,
wschmidt@linux.vnet.ibm.com
Subject: Re: Backports to 6 (and 7, and 5)
Date: Tue, 27 Jun 2017 07:18:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1706270916250.23185@zhemvz.fhfr.qr> (raw)
In-Reply-To: <1498516276-16423-1-git-send-email-segher@kernel.crashing.org>
On Mon, 26 Jun 2017, Segher Boessenkool wrote:
> Hi!
>
> I'd like to backport the following patches to 7, 6, and where
> applicable 5 (some are in 7 already).
>
>
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg02107.html
> Fix expand_builtin_atomic_fetch_op for pre-op (PR80902)
>
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01404.html
> Fix comparison of decimal float zeroes (PR80692)
>
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00819.html
> IRA: Don't create new regs for debug insns (PR80429)
>
> https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01050.html
> lra: A multiple_sets is not a simple_move_p (PR73650)
The above look ok.
> 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).
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00003.html
> simplify-rtx: Fix compare of comparisons (PR60818)
Ok.
Thanks,
Richard.
>
> Are those okay to backport?
>
>
> And, rs6000 patches:
>
> https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00567.html
> rs6000: Don't add an immediate to r0 (PR80966)
>
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg02408.html
> rs6000: Don't write "nor" as (not (ior () ())) (PR80618)
>
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00568.html
> rs6000: Enforce quad_address_p in TImode atomic_load/store (PR80382)
>
> https://gcc.gnu.org/ml/gcc-patches/2017-01/msg01543.html
> rs6000: Small varargs for BE SVR4 (PR61729, PR77850)
>
>
> Segher
>
>
--
Richard Biener <rguenther@suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
next prev parent reply other threads:[~2017-06-27 7:18 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 [this message]
2017-06-27 16:02 ` Segher Boessenkool
2017-06-27 17:36 ` Jakub Jelinek
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=alpine.LSU.2.20.1706270916250.23185@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).