CVS difference for ais/ai-00133.txt

Differences between 1.16 and version 1.17
Log of other versions for file ais/ai-00133.txt

--- ais/ai-00133.txt	2005/06/16 23:47:06	1.16
+++ ais/ai-00133.txt	2005/08/21 06:00:09	1.17
@@ -1,4 +1,4 @@
-!standard 13.05.03 (08)                               04-09-28  AI95-00133/05
+!standard 13.05.03 (08)                               05-08-09  AI95-00133/06
 !standard 13.03 (08)
 !standard 13.05.01 (10)
 !standard 13.05.01 (13)
@@ -23,7 +23,7 @@
 
 The interpretation of component_clauses in the nondefault bit order is based on
 *machine scalars*, which are chunks of storage that can be natively loaded and
-stored by the machine. All the component_clauses at a given offset are
+stored by the machine. All of the component_clauses at a given offset are
 considered to be part of the same machine scalar, and the first_bit and
 last_bit are interpreted as bit offsets within that machine scalar. This makes
 it possible to write endian-independent record_representation_clauses.
@@ -91,7 +91,7 @@
 equal to the size of the largest machine scalar directly specify the position
 and size of the corresponding component;
 
-o   for other component_clauses, all the components having the same value of
+o   for other component_clauses, all of the components having the same value of
 position are considered to be part of a single machine scalar, located at that
 position; this machine scalar has a size which is the smallest machine scalar
 size larger than the largest last_bit for all component_clauses at that
@@ -101,10 +101,15 @@
 
 Add after 13.5.1(17):
 
-o  An implementation should support machine scalars that correspond to all the
-integer, floating point, and address formats supported by the machine.
+o  An implementation should support machine scalars that correspond to all of
+the integer, floating point, and address formats supported by the machine.
 
+Replace 13.5.1(20) by:
 
+o  For a component with a subtype whose Size is less than the word size, any
+   storage place that does not cross an aligned word boundary should be
+   supported.
+
 Replace 13.5.2(2-4) by:
 
 R.C'Position
@@ -363,7 +368,7 @@
 greater than or equal to the size of the largest machine scalar directly
 specify the position and size of the corresponding component;>
 
-@xbullet<for other @fa<component_clause>s, all the components having the
+@xbullet<for other @fa<component_clause>s, all of the components having the
 same value of @fa<position> are considered to be part of a single machine
 scalar, located at that @fa<position>; this machine scalar has a size which is
 the smallest machine scalar size larger than the largest @fa<last_bit> for all
@@ -378,8 +383,21 @@
 The recommended level of support for @fa<record_representation_clause>s is:
 @dinst
 @xbullet<An implementation should support machine scalars that correspond to
-all the integer, floating point, and address formats supported by the machine.>
+all of the integer, floating point, and address formats supported by the
+machine.>
+
+
+!corrigendum 13.5.1(20)
 
+@drepl
+@xbullet<If the default bit ordering applies to the declaration of a given
+type, then for a component whose subtype's Size is less than the word size, any
+storage place that does not cross an aligned word boundary should be
+supported.>
+@dby
+@xbullet<For a component with a subtype whose Size is less than the word size,
+any storage place that does not cross an aligned word boundary should be
+supported.>
 
 !corrigendum 13.5.2(02)
 

Questions? Ask the ACAA Technical Agent