procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

inline-asm: Clarify documentation of operand syntax [PR67301]

Browse source 
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.
This commit is contained in:
Sandra Loosemore 2025-03-08 05:23:55 +00:00
parent 3014f87871
commit f0ff753962
1 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
gcc/doc/extend.texi
View file

@ -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.