From: Eric Botcazou <ebotca...@adacore.com>
gcc/ada/
* doc/gnat_rm/standard_and_implementation_defined_restrictions.rst
(No_Dependence): Give examples of new No_Dependence restrictions.
* gnat_rm.texi: Regenerate.
Tested on x86_64-pc-linux-gnu, committed on master.
---
...nd_implementation_defined_restrictions.rst | 12 ++++++-
gcc/ada/gnat_rm.texi | 33 ++++++++++++++++++-
2 files changed, 43 insertions(+), 2 deletions(-)
diff --git
a/gcc/ada/doc/gnat_rm/standard_and_implementation_defined_restrictions.rst
b/gcc/ada/doc/gnat_rm/standard_and_implementation_defined_restrictions.rst
index f8e2a58595f..275b46c3712 100644
--- a/gcc/ada/doc/gnat_rm/standard_and_implementation_defined_restrictions.rst
+++ b/gcc/ada/doc/gnat_rm/standard_and_implementation_defined_restrictions.rst
@@ -186,7 +186,17 @@ No_Dependence
[RM 13.12.1] This restriction ensures at compile time that there are no
dependences on a library unit. For GNAT, this includes implicit implementation
dependences on units of the runtime library that are created by the compiler
-to support specific constructs of the language.
+to support specific constructs of the language. Here are some examples:
+
+* ``System.Arith_64``: 64-bit arithmetics for 32-bit platforms,
+* ``System.Arith_128``: 128-bit arithmetics for 64-bit platforms,
+* ``System.Memory``: heap memory allocation routines,
+* ``System.Memory_Compare``: memory comparison routine (aka ``memcmp`` for C),
+* ``System.Memory_Copy``: memory copy routine (aka ``memcpy`` for C),
+* ``System.Memory_Move``: memoy move routine (aka ``memmove`` for C),
+* ``System.Memory_Set``: memory set routine (aka ``memset`` for C),
+* ``System.Stack_Checking[.Operations]``: stack checking without MMU,
+* ``System.GCC``: support routines from the GCC library.
No_Direct_Boolean_Operators
---------------------------
diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi
index 5e05287d6d8..3818f22414a 100644
--- a/gcc/ada/gnat_rm.texi
+++ b/gcc/ada/gnat_rm.texi
@@ -12727,7 +12727,38 @@ delay statements and no semantic dependences on
package Calendar.
[RM 13.12.1] This restriction ensures at compile time that there are no
dependences on a library unit. For GNAT, this includes implicit implementation
dependences on units of the runtime library that are created by the compiler
-to support specific constructs of the language.
+to support specific constructs of the language. Here are some examples:
+
+
+@itemize *
+
+@item
+@code{System.Arith_64}: 64-bit arithmetics for 32-bit platforms,
+
+@item
+@code{System.Arith_128}: 128-bit arithmetics for 64-bit platforms,
+
+@item
+@code{System.Memory}: heap memory allocation routines,
+
+@item
+@code{System.Memory_Compare}: memory comparison routine (aka @code{memcmp} for
C),
+
+@item
+@code{System.Memory_Copy}: memory copy routine (aka @code{memcpy} for C),
+
+@item
+@code{System.Memory_Move}: memoy move routine (aka @code{memmove} for C),
+
+@item
+@code{System.Memory_Set}: memory set routine (aka @code{memset} for C),
+
+@item
+@code{System.Stack_Checking[.Operations]}: stack checking without MMU,
+
+@item
+@code{System.GCC}: support routines from the GCC library.
+@end itemize
@node No_Direct_Boolean_Operators,No_Dispatch,No_Dependence,Partition-Wide
Restrictions
@anchor{gnat_rm/standard_and_implementation_defined_restrictions
no-direct-boolean-operators}@anchor{1ca}
--
2.40.0
