diff options
Diffstat (limited to 'gcc/ada/doc/gnat_rm')
| -rw-r--r-- | gcc/ada/doc/gnat_rm/implementation_defined_characteristics.rst | 12 | ||||
| -rw-r--r-- | gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst | 35 |
2 files changed, 18 insertions, 29 deletions
diff --git a/gcc/ada/doc/gnat_rm/implementation_defined_characteristics.rst b/gcc/ada/doc/gnat_rm/implementation_defined_characteristics.rst index 5399bda..3e41899 100644 --- a/gcc/ada/doc/gnat_rm/implementation_defined_characteristics.rst +++ b/gcc/ada/doc/gnat_rm/implementation_defined_characteristics.rst @@ -478,12 +478,12 @@ via compiler switches such as "-gnata". * "Implementation-defined check names. See 11.5(27)." -The implementation defined check names include Alignment_Check, -Atomic_Synchronization, Container_Checks, Duplicated_Tag_Check, -Predicate_Check, Raise_Check, Tampering_Check, and Validity_Check. -In addition, a user program can add implementation-defined check -names by means of the pragma Check_Name. See the description of -pragma ``Suppress`` for full details. +The implementation-defined check names include Alignment_Check, +Container_Checks, Duplicated_Tag_Check, Predicate_Check, +Raise_Check, Tampering_Check, and Validity_Check. In addition, a +user program can add implementation-defined check names by means +of the pragma Check_Name. See the description of pragma +``Suppress`` for details. * "Existence and meaning of second parameter of pragma Unsuppress. diff --git a/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst b/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst index 7ff94c4..61ed40e 100644 --- a/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst +++ b/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst @@ -1662,18 +1662,20 @@ Syntax: pragma Disable_Atomic_Synchronization [(Entity)]; + pragma Enable_Atomic_Synchronization [(Entity)]; Ada requires that accesses (reads or writes) of an atomic variable be regarded as synchronization points in the case of multiple tasks. Particularly in the case of multi-processors this may require special -handling, e.g. the generation of memory barriers. This capability may -be turned off using this pragma in cases where it is known not to be -required. - -The placement and scope rules for this pragma are the same as those -for ``pragma Suppress``. In particular it can be used as a -configuration pragma, or in a declaration sequence where it applies -till the end of the scope. If an ``Entity`` argument is present, +handling, e.g. the generation of memory barriers. This synchronization +is performed by default, but can be turned off using pragma +``Disable_Atomic_Synchronization``. +The ``Enable_Atomic_Synchronization`` pragma turns it back on. + +The placement and scope rules for these pragmas are the same as those +for ``pragma Suppress``. In particular they can be used as +configuration pragmas, or in a declaration sequence where they apply +until the end of the scope. If an ``Entity`` argument is present, the action applies only to that entity. Pragma Dispatching_Domain @@ -1903,21 +1905,8 @@ Syntax: pragma Enable_Atomic_Synchronization [(Entity)]; - -Ada requires that accesses (reads or writes) of an atomic variable be -regarded as synchronization points in the case of multiple tasks. -Particularly in the case of multi-processors this may require special -handling, e.g. the generation of memory barriers. This synchronization -is performed by default, but can be turned off using -``pragma Disable_Atomic_Synchronization``. The -``Enable_Atomic_Synchronization`` pragma can be used to turn -it back on. - -The placement and scope rules for this pragma are the same as those -for ``pragma Unsuppress``. In particular it can be used as a -configuration pragma, or in a declaration sequence where it applies -till the end of the scope. If an ``Entity`` argument is present, -the action applies only to that entity. +Reenables atomic synchronization; see ``pragma Disable_Atomic_Synchronization`` +for details. Pragma Exceptional_Cases ======================== |