summaryrefslogtreecommitdiffstats
path: root/gcc/ada/einfo.ads
diff options
context:
space:
mode:
authorcharlet <charlet@138bc75d-0d04-0410-961f-82ee72b054a4>2009-06-21 13:11:41 +0000
committercharlet <charlet@138bc75d-0d04-0410-961f-82ee72b054a4>2009-06-21 13:11:41 +0000
commit6d081ca682d17682b70f7ba62ef64659f27d12ff (patch)
tree87c0a4e21c018577dc730113e375474d9d50f886 /gcc/ada/einfo.ads
parent5eabd16b31b0ef13bc7f3a04fdd6dad04b62f1fe (diff)
downloadppe42-gcc-6d081ca682d17682b70f7ba62ef64659f27d12ff.tar.gz
ppe42-gcc-6d081ca682d17682b70f7ba62ef64659f27d12ff.zip
2009-06-21 Ed Falis <falis@adacore.com>
* env.c (__gnat_environ): return NULL for vThreads - unimplemented 2009-06-21 Eric Botcazou <ebotcazou@adacore.com> * einfo.ads: Update comments. 2009-06-21 Hristian Kirtchev <kirtchev@adacore.com> * sem_disp.adb (Check_Direct_Call): New routine. Dispatching calls where the controlling formal is of private class-wide type whose completion is a synchronized type can be converted into direct calls. 2009-06-21 Vincent Celier <celier@adacore.com> * gnatcmd.adb (Check_Files): When all sources of the project are to be indicated to gnatcheck, gnatpp or gnatmetric, always specify the list of sources using -files=, so that the distinction can be made by the tool of a call with no source (to display the usage) from a call with a project file that contains no source. 2009-06-21 Jerome Lambourg <lambourg@adacore.com> * exp_ch3.adb (Build_Array_Init_Proc): Do not build the init proc in case of VM convention arrays. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@148763 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/ada/einfo.ads')
-rw-r--r--gcc/ada/einfo.ads9
1 files changed, 6 insertions, 3 deletions
diff --git a/gcc/ada/einfo.ads b/gcc/ada/einfo.ads
index 049faab5a2b..29eea5ecce5 100644
--- a/gcc/ada/einfo.ads
+++ b/gcc/ada/einfo.ads
@@ -239,9 +239,12 @@ package Einfo is
-- The RM_Size field keeps track of the RM Size as needed in these
-- three situations.
--- For types other than discrete and fixed-point types, the Object_Size
--- and Value_Size are the same (and equivalent to the RM attribute Size).
--- Only Size may be specified for such types.
+-- For elementary types other than discrete and fixed-point types, the
+-- Object_Size and Value_Size are the same (and equivalent to the RM
+-- attribute Size). Only Size may be specified for such types.
+
+-- For composite types, Object_Size and Value_Size are computed from their
+-- respective value for the type of each element as well as the layout.
-- All size attributes are stored as Uint values. Negative values are used to
-- reference GCC expressions for the case of non-static sizes, as explained
OpenPOWER on IntegriCloud