CVS difference for ais/ai-00259.txt

Differences between 1.5 and version 1.6
Log of other versions for file ais/ai-00259.txt

--- ais/ai-00259.txt	2003/01/24 04:14:27	1.5
+++ ais/ai-00259.txt	2003/03/04 04:56:22	1.6
@@ -1,6 +1,7 @@
-!standard  C.6 (16)                                    03-01-15  AI95-00259/03
-!standard  C.6 (21)
+!standard  C.6 (21)                                    03-02-20  AI95-00259/04
 !class binding interpretation 03-01-10
+!status Amendment 200Y 03-02-20
+!status ARG Approved 8-0-0  03-02-09
 !status work item 02-04-19
 !status received 01-02-12
 !qualifier Omission
@@ -73,16 +74,6 @@
 required to document that, so users will know if an implementation is suitable
 for accessing hardware directly.
 
-!corrigendum C.06(16)
-
-@drepl
-For a volatile object all reads and updates of the object as a whole are
-performed directly to memory.
-@dby
-For a volatile object all reads and updates of the object as a whole are
-performed directly to memory, and shall not be combined with reads or updates
-of other objects.
-
 !corrigendum C.06(21)
 
 @dinsa
@@ -91,9 +82,10 @@
 for which it can support indivisible reads and updates.
 @dinss
 @i<@s8<Implementation Advice>>
+
 A load or store of a volatile object whose size is a multiple of
-System.Storage_Unit should be implemented by accessing exactly the bits of the
-object and no others.
+System.Storage_Unit and whose alignment is nonzero, should be implemented by
+accessing exactly the bits of the object and no others.
 
 A load or store of an atomic object should, where possible, be implemented
 by a single load or store instruction.

Questions? Ask the ACAA Technical Agent