CVS difference for ai05s/ai05-0201-1.txt

--- ai05s/ai05-0201-1.txt	2010/02/23 07:31:06	1.2
+++ ai05s/ai05-0201-1.txt	2011/03/12 06:44:35	1.3
@@ -1,7 +1,9 @@
-!standard  9.10(1/3)                               10-02-12    AI05-0201-1/01
+!standard  9.10(1/3)                               11-03-11    AI05-0201-1/02
 !standard  C.6(22/2)
 !standard  C.6(23/2)
 !class binding interpretation 10-02-12
+!status Amendment 2012 11-03-11
+!status ARG Approved  7-0-0  10-02-20
 !status work item 10-02-12
 !status received 09-11-10
 !priority Low
@@ -11,7 +13,8 @@
 
 !summary
 
-** TBD **
+Components of an atomic composite object are not necessarily
+independently-addressable.
 
 !question
 
@@ -68,7 +71,8 @@
 C.6(22)).
 
 Should pragma Atomic on a composite object or type imply components are not
-independently addressable? (Not exactly.)
+independently addressable? (No, but it can effect whether the components are
+independently addressable.)
 
 !recommendation
 
@@ -86,12 +90,13 @@
 two nonoverlapping objects are independently addressable
 except when they are both parts of a composite object for which
 a non-confirming representation item is used to specify
-packing, record layout, Component_Size, Atomic, or convention, in which
+packing, record layout, Component_Size, {Atomic, }or convention, in which
 case it is unspecified whether the parts are independently addressable.
 
 Add to AARM 9.10(1.d/3):
 
-This does not apply to the components of the atomic object, however.
+Note, however, that the components of an atomic object are not necessarily
+atomic.
 
 !discussion
 
@@ -123,8 +128,30 @@
 IA. Also, implementations are always allowed to go beyond the IA, but they can't
 ignore language rules to do so.]
 
---!corrigendum 3.9.3(4/2)
+!corrigendum 9.10(1/3)
 
+@drepl
+If two different objects, including nonoverlapping parts of the same
+object, are @i<independently addressable>, they can be manipulated
+concurrently by two different tasks without synchronization.
+Any two nonoverlapping objects are independently addressable if
+either object is specified as independently addressable (see C.6). Otherwise,
+two nonoverlapping objects are independently addressable
+except when they are both parts of a composite object for which
+a non-confirming representation item is used to specify
+packing, record layout, Component_Size, or convention, in which case
+it is unspecified whether the parts are independently addressable.
+@dby
+If two different objects, including nonoverlapping parts of the same
+object, are @i<independently addressable>, they can be manipulated
+concurrently by two different tasks without synchronization.
+Any two nonoverlapping objects are independently addressable if
+either object is specified as independently addressable (see C.6). Otherwise,
+two nonoverlapping objects are independently addressable
+except when they are both parts of a composite object for which
+a non-confirming representation item is used to specify
+packing, record layout, Component_Size, Atomic, or convention, in which case
+it is unspecified whether the parts are independently addressable.
 
 !ACATS Test