From: Eric Botcazou <[email protected]>
gcc/ada/ChangeLog:
* doc/gnat_ugn/building_executable_programs_with_gnat.rst: Fix a
couple of glitches.
* 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/gnat_ugn.texi | 4 ++--
2 files changed, 4 insertions(+), 4 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 32c5d6efa71..c69b958804c 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
@@ -8021,7 +8021,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:`-fstack-check` 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
@@ -8029,7 +8029,7 @@ small amount of stack and the total stack depth exceeds
the amount of
available stack, the program will be terminated by a signal instead of
raising an Ada exception.
-GNAT LLVM doesn't support the ``Scalar_Storage_Order`` pragma except when
+GNAT LLVM doesn't support the ``Scalar_Storage_Order`` attribute except when
it's used to confirm the chosen storage order. This is because this facility
is provided by GCC but not by LLVM.
diff --git a/gcc/ada/gnat_ugn.texi b/gcc/ada/gnat_ugn.texi
index 567caabd14e..6350a4a99ef 100644
--- a/gcc/ada/gnat_ugn.texi
+++ b/gcc/ada/gnat_ugn.texi
@@ -17587,7 +17587,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 @code{-fcheck-stack} switch.
+GNAT LLVM doesn’t fully implement the @code{-fstack-check} 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
@@ -17595,7 +17595,7 @@ small amount of stack and the total stack depth exceeds
the amount of
available stack, the program will be terminated by a signal instead of
raising an Ada exception.
-GNAT LLVM doesn’t support the @code{Scalar_Storage_Order} pragma except when
+GNAT LLVM doesn’t support the @code{Scalar_Storage_Order} attribute except when
it’s used to confirm the chosen storage order. This is because this facility
is provided by GCC but not by LLVM.
--
2.53.0
