From 63e21a7237fac8dfedda51cc7f4089e8c07a25e9 Mon Sep 17 00:00:00 2001 From: Eric Botcazou Date: Fri, 13 Dec 2019 09:04:33 +0000 Subject: [Ada] Minor tweak to Volatile_Full_Access wording in GNAT RM 2019-12-13 Eric Botcazou gcc/ada/ * doc/gnat_rm/implementation_defined_pragmas.rst: Minor tweak to Volatile_Full_Access wording in GNAT RM. * gnat_rm.texi: Regenerate. From-SVN: r279354 --- gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'gcc/ada/doc') diff --git a/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst b/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst index bf0a9d4..fd66aed 100644 --- a/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst +++ b/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst @@ -7425,8 +7425,8 @@ Syntax: This is similar in effect to pragma Volatile, except that any reference to the object is guaranteed to be done only with instructions that read or write all the bits of the object. Furthermore, if the object is of a composite type, -then any reference to a component of the object is guaranteed to read and/or -write all the bits of the object. +then any reference to a subcomponent of the object is guaranteed to read +and/or write all the bits of the object. The intention is that this be suitable for use with memory-mapped I/O devices on some machines. Note that there are two important respects in which this is @@ -7438,7 +7438,7 @@ is not to the whole object; the compiler is allowed (and generally will) access only part of the object in this case. It is not permissible to specify ``Atomic`` and ``Volatile_Full_Access`` for -the same object. +the same type or object. It is not permissible to specify ``Volatile_Full_Access`` for a composite (record or array) type or object that has at least one ``Aliased`` component. -- cgit v1.1