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

doc: Quote singular '=' signs

Browse source 
gcc:
	* doc/extend.texi (Attribute Syntax): Use @samp{=} instead of @code{=}.
	(Extended Asm): Ditto.
This commit is contained in:
Gerald Pfeifer 2024-05-26 23:48:36 +02:00
parent 95660223c4
commit 53d919873c
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
gcc/doc/extend.texi
View file

@ -10026,7 +10026,7 @@ labelled in C90 or C99, so the ambiguity does not arise there.
@subsubheading Enumerator Attributes
In GNU C, an attribute specifier list may appear as part of an enumerator.
The attribute goes after the enumeration constant, before @code{=}, if
The attribute goes after the enumeration constant, before @samp{=}, if
present. The optional attribute in the enumerator appertains to the
enumeration constant. It is not possible to place the attribute after
the constant expression, if present.
@ -10108,7 +10108,7 @@ the @code{noreturn} attribute applies to all the functions
declared; the @code{format} attribute only applies to @code{d1}.
An attribute specifier list may appear immediately before the comma,
@code{=} or semicolon terminating the declaration of an identifier other
@samp{=}, or semicolon terminating the declaration of an identifier other
than a function definition. Such attribute specifiers apply
to the declared object or function. Where an
assembler name for an object or function is specified (@pxref{Asm
@ -11804,7 +11804,7 @@ stop:
The following artificial example shows an @code{asm goto} that sets
up an output only on one path inside the @code{asm goto}. Usage of
constraint modifier @code{=} instead of @code{+} would be wrong as
constraint modifier @samp{=} instead of @samp{+} would be wrong as
@code{factor} is used on all paths from the @code{asm goto}.
@example