se if LTO was used.) So I now have a real-world
> example of the situation where you need an early-clobber on tied
> outputs, and also where an early-clobber is undesirable.
>
> Revised and expanded.
>
> * doc/extend.texi (Extended Asm ): Rename to
> "Clobbers
On Tue, Aug 22, 2017 at 01:41:21PM +0930, Alan Modra wrote:
> + "#n=%1 ap=%8=%12 lda=%13 x=%7=%10 y=%0=%2 alpha=%9 o16=%11\n"
> + "#a0=%3 a1=%4 a2=%5 a3=%6"
> + :
> + "+m" (*(double (*)[n]) y),
> + "+r" (n), // 1
Another small revision. That needs to be "+&r" (n), in c
need an early-clobber on tied
outputs, and also where an early-clobber is undesirable.
Revised and expanded.
* doc/extend.texi (Extended Asm ): Rename to
"Clobbers and Scratch Registers". Add paragraph on
alternative to clobbers for scratch registers and OpenBLAS
* doc/extend.texi (Extended Asm ): Rename to
> "Clobbers and Scratch Registers". Add paragraph on
> alternative to clobbers for scratch registers and OpenBLAS
> example.
>
> diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
> index 940490e..0637672
use any of the clobbered registers
-(@pxref{Clobbers}).
+(@pxref{Clobbers and Scratch Registers}).
Output operand expressions must be lvalues. The compiler cannot check whether
the operands have data types that are reasonable for the instruction being
@@ -8671,7 +8671,8 @@ as input. The
