From: Richard Kenner <ken...@adacore.com>
gcc/ada/ChangeLog:
* doc/gnat_ugn/building_executable_programs_with_gnat.rst: Fix minor
markup errors.
* doc/gnat_ugn/gnat_utility_programs.rst: Likewise.
* gnat_ugn.texi: Regenerate.
Tested on x86_64-pc-linux-gnu, committed on master.
---
.../doc/gnat_ugn/building_executable_programs_with_gnat.rst | 4 ++--
gcc/ada/doc/gnat_ugn/gnat_utility_programs.rst | 2 +-
gcc/ada/gnat_ugn.texi | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
b/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
index e6b87bddaab..51a9201bc5b 100644
--- a/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
+++ b/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
@@ -8077,7 +8077,7 @@ is either an ``out`` parameter or the function return
value, if any.
The debug information reflects these transformations and not the original
Ada source code.
-GNAT LLVM doesn't fully implement the :switch:``-fcheck-stack`` switch.
+GNAT LLVM doesn't fully implement the :switch:`-fcheck-stack` switch.
When you specify it, the code generated by GNAT LLVM tests for allocating
overly-large items on the stack, but not all cases of stack overflow. For
example, if you have a very deep recursion where each call only uses a
@@ -8123,7 +8123,7 @@ We provide two options that you can use to build code
with GNAT LLVM:
*GPRbuild and GPR Companion Tools User's Guide* for details. You
can determine from the first line of the :file:`.ali` file
which version of GNAT built that file because it contains either
- :code:``GNAT`` or :code:``GNAT-LLVM``.
+ :code:`GNAT` or :code:`GNAT-LLVM`.
.. only:: PRO
diff --git a/gcc/ada/doc/gnat_ugn/gnat_utility_programs.rst
b/gcc/ada/doc/gnat_ugn/gnat_utility_programs.rst
index 4115a402c4d..d1011be2c0b 100644
--- a/gcc/ada/doc/gnat_ugn/gnat_utility_programs.rst
+++ b/gcc/ada/doc/gnat_ugn/gnat_utility_programs.rst
@@ -1266,7 +1266,7 @@ building specialized scripts.
defining occurrences appear exactly as in the source file where they
are declared. The other values for this switch --
:switch:`--name-upper-case`, :switch:`--name-lower-case`, and
- :switch:``--name-mixed-case``
+ :switch:`--name-mixed-case`
-- result in upper, lower, or mixed case, respectively. If
``gnatpp`` changes the casing of a defining occurrence, it
similarly changes the casing of all the usage occurrences of this
diff --git a/gcc/ada/gnat_ugn.texi b/gcc/ada/gnat_ugn.texi
index e4f14d231d4..18976805005 100644
--- a/gcc/ada/gnat_ugn.texi
+++ b/gcc/ada/gnat_ugn.texi
@@ -17594,7 +17594,7 @@ is either an @code{out} parameter or the function
return value, if any.
The debug information reflects these transformations and not the original
Ada source code.
-GNAT LLVM doesn’t fully implement the :switch:@code{-fcheck-stack} switch.
+GNAT LLVM doesn’t fully implement the @code{-fcheck-stack} switch.
When you specify it, the code generated by GNAT LLVM tests for allocating
overly-large items on the stack, but not all cases of stack overflow. For
example, if you have a very deep recursion where each call only uses a
@@ -17635,7 +17635,7 @@ file with @code{gprconfig} and using it with
@code{gprbuild}; see the
`GPRbuild and GPR Companion Tools User’s Guide' for details. You
can determine from the first line of the @code{.ali} file
which version of GNAT built that file because it contains either
-:code:@code{GNAT} or :code:@code{GNAT-LLVM}.
+@code{GNAT} or @code{GNAT-LLVM}.
@end itemize
--
2.43.0
