From: Peter Bergner <bergner@vnet.ibm.com>
To: Carl Love <cel@us.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
gcc-patches@gcc.gnu.org,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH,rs6000] GCC -7, no swap optimization for vpermxor instruction
Date: Thu, 22 Mar 2018 03:45:00 -0000 [thread overview]
Message-ID: <23494b04-1a95-01bc-7d37-00d19c9b0d5b@vnet.ibm.com> (raw)
In-Reply-To: <1521670598.4859.11.camel@us.ibm.com>
On 3/21/18 5:16 PM, Carl Love wrote:
> The following patch is a back port from mainlin of a fix for
[snip]
>
> 2018-03-21 Carl Love <cel@us.ibm.com>
>
> * config/rs6000/r6000.c (rtx_is_swappable_p): Add case UNSPEC_VPERMXOR.
>
> gcc/testsuite/ChangeLog:
>
> 2018-03-21 Carl Love <cel@us.ibm.com>
> * gcc.target/powerpc/crypto-builtin-1-runnable.c: New test file.
Since this is a backport from mainline, your ChangeLog entry needs mention
that fact. Also, is the mainline patch associated with a bugzilla entry?
If so, that also needs to be included. See for example the following
patch submission and what its ChangeLog entries look like:
https://gcc.gnu.org/ml/gcc-patches/2018-01/msg01869.html
Peter
next prev parent reply other threads:[~2018-03-22 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 22:19 Carl Love
2018-03-22 3:45 ` Peter Bergner [this message]
2018-03-22 23:01 ` Segher Boessenkool
2018-03-22 16:08 Carl Love
2018-03-22 18:35 ` Peter Bergner
2018-03-22 23:37 ` 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=23494b04-1a95-01bc-7d37-00d19c9b0d5b@vnet.ibm.com \
--to=bergner@vnet.ibm.com \
--cc=cel@us.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).