From 0099b5baa9d2d1b3623610160d07de6e6c303f10 Mon Sep 17 00:00:00 2001 From: meissner Date: Wed, 10 Jun 2015 16:51:49 +0000 Subject: [PATCH] 2015-06-10 Michael Meissner PR target/66474 * doc/md.texi (Machine Constraints): Document that on the PowerPC if you use a constraint that targets a VSX register, you must use %x in the template. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@224332 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 7 +++++++ gcc/doc/md.texi | 21 +++++++++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 7c002a4..e4dfe38 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2015-06-10 Michael Meissner + + PR target/66474 + * doc/md.texi (Machine Constraints): Document that on the PowerPC + if you use a constraint that targets a VSX register, you must use + %x in the template. + 2015-06-10 Max Filippov * config/xtensa/xtensa.h (TARGET_DEBUG): New definition. diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index 30d7775..e991286 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -3070,6 +3070,27 @@ Altivec vector register @item wa Any VSX register if the -mvsx option was used or NO_REGS. +When using any of the register constraints (@code{wa}, @code{wd}, +@code{wf}, @code{wg}, @code{wh}, @code{wi}, @code{wj}, @code{wk}, +@code{wl}, @code{wm}, @code{ws}, @code{wt}, @code{wu}, @code{wv}, +@code{ww}, or @code{wy}) that take VSX registers, you must use +@code{%x} in the template so that the correct register is used. +Otherwise the register number output in the assembly file will be +incorrect if an Altivec register is an operand of a VSX instruction +that expects VSX register numbering. + +@smallexample +asm ("xvadddp %x0,%x1,%x2" : "=wa" (v1) : "wa" (v2), "wa" (v3)); +@end smallexample + +is correct, but: + +@smallexample +asm ("xvadddp %0,%1,%2" : "=wa" (v1) : "wa" (v2), "wa" (v3)); +@end smallexample + +is not correct. + @item wd VSX vector register to hold vector double data or NO_REGS. -- 2.7.4