From f0ff7539626e25341c1b450b537e69f86e0bd1f6 Mon Sep 17 00:00:00 2001 From: Sandra Loosemore Date: Sat, 8 Mar 2025 05:23:55 +0000 Subject: [PATCH] inline-asm: Clarify documentation of operand syntax [PR67301] gcc/ChangeLog PR c/67301 * doc/extend.texi (Extended Asm): Clarify that the square brackets around the asmSymbolicName of operands are a required part of the syntax. --- gcc/doc/extend.texi | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 13cbc72ed24..5e40cf8387b 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -11473,10 +11473,11 @@ Operands are separated by commas. Each operand has this format: @table @var @item asmSymbolicName -Specifies a symbolic name for the operand. -Reference the name in the assembler template -by enclosing it in square brackets -(i.e.@: @samp{%[Value]}). The scope of the name is the @code{asm} statement +Specifies an optional symbolic name for the operand. The literal square +brackets @samp{[]} around the @var{asmSymbolicName} are required both +in the operand specification and references to the operand in the assembler +template, i.e.@: @samp{%[Value]}. +The scope of the name is the @code{asm} statement that contains the definition. Any valid C variable name is acceptable, including names already defined in the surrounding code. No two operands within the same @code{asm} statement can use the same symbolic name. @@ -11762,10 +11763,11 @@ Operands are separated by commas. Each operand has this format: @table @var @item asmSymbolicName -Specifies a symbolic name for the operand. -Reference the name in the assembler template -by enclosing it in square brackets -(i.e.@: @samp{%[Value]}). The scope of the name is the @code{asm} statement +Specifies an optional symbolic name for the operand. The literal square +brackets @samp{[]} around the @var{asmSymbolicName} are required both +in the operand specification and references to the operand in the assembler +template, i.e.@: @samp{%[Value]}. +The scope of the name is the @code{asm} statement that contains the definition. Any valid C variable name is acceptable, including names already defined in the surrounding code. No two operands within the same @code{asm} statement can use the same symbolic name.