[Bug c/112391] New: inline-asm documentation wording for implicitly volatile can be cause confusion

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112391

            Bug ID: 112391
           Summary: inline-asm documentation wording for implicitly
                    volatile can be cause confusion
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: c
          Assignee: pinskia at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Reading:
https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Extended-Asm.html
https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html

It current reads:
```
asm statements that have no output operands and asm goto statements, are
implicitly volatile.
```

this can be slightly confusing is the requirement that the asm statement has no
output operands and an asm goto or is it both are implicitly volatile. Knowing
GCC and fixing PR 103979 (asm goto with output operands) myself, I know this is
supposed to be it is both get added the volatile:
* asm statements with no output operands
* asm goto statements