On 3/22/18 10:48 AM, Carl Love wrote:
> Backport: UNSPEC_VPERMXOR fix from mainline commit 258530:
> 2018-03-21 Carl Love <c...@us.ibm.com>
>
> * config/rs6000/r6000.c (rtx_is_swappable_p): Add case UNSPEC_VPERMXOR.
>
> gcc/testsuite/ChangeLog:
>
> 2018-03-21 Carl Love <c...@us.ibm.com>
> * gcc.target/powerpc/crypto-builtin-1-runnable.c: New test file.
Still not the right syntax. From the URL I provided you, it shows your
ChangeLog entries for your backport should look like:
gcc/ChangeLog:
2018-03-22 Carl Love <c...@us.ibm.com>
Backport from mainline
2018-03-14 Carl Love <c...@us.ibm.com>
* config/rs6000/rs6000-c.c: Add macro definitions for
ALTIVEC_BUILTIN_VEC_PERMXOR.
* config/rs6000/rs6000.h: Add #define for vec_permxor builtin.
* config/rs6000/rs6000-builtin.def: Add macro expansions for VPERMXOR.
* config/rs6000/altivec.md (altivec_vpermxor): New define expand.
* config/rs6000/rs6000-p8swap.c (rtx_is_swappable_p): Add case
UNSPEC_VPERMXOR.
* config/doc/extend.texi: Add prototypes for vec_permxor.
gcc/testsuite/ChangeLog:
2018-03-22 Carl Love <c...@us.ibm.com>
Backport from mainline
2018-03-14 Carl Love <c...@us.ibm.com>
* gcc.target/powerpc/builtins-7-runnable.c: New test file.
So basically, you cut/paste the entire ChangeLog entry from the trunk
ChangeLog file, including the date stamp (tabbed over) with the line
"Backport from mainline" added. You then add a new date stamp which
is the date you commit the patch. If you post a patch with a date stamp
and you commit it a different day, you need to update the date stamp.
Most people leave the date stamp (not the one after the Backport from
mainline) out of their patch submissions, since they don't know ahead
of time when they will commit it.
Peter
