From: Kelvin Nilsen <kdnilsen@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@gcc.gnu.org>
Subject: Backports to gcc 6.x
Date: Tue, 11 Jul 2017 22:43:00 -0000 [thread overview]
Message-ID: <356a6d46-cac4-0d9d-63ec-06689c10803f@linux.vnet.ibm.com> (raw)
I would like to backport the following patches to the GCC 6 branch.
PR66669: Fix failure of gcc.dg/loop-8.c on Power
https://gcc.gnu.org/ml/gcc-patches/2017-01/msg01788.html
PR68972: g++.dg/cpp1y/vla-initlist1.C test case fails on power
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg00541.html
Handle conflicting target options -mno-power9-vector and -mcpu=power9
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01192.html
PR80103: Fix ICE with cross compiler
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01335.html
PR80101: Fix ICE in store_data_bypass_p
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00953.html
Each of these patches has been bootstrapped and regression tested on the
GCC 6 branch. In backport, patch PR80103 omits certain changes to
existing comments that are not present in GCC6.
Are these patches ok for backporting to GCC 6?
next reply other threads:[~2017-07-11 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 22:43 Kelvin Nilsen [this message]
2017-07-12 12:26 ` Segher Boessenkool
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=356a6d46-cac4-0d9d-63ec-06689c10803f@linux.vnet.ibm.com \
--to=kdnilsen@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@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: 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).