diff options
author | Arnaud Charlet <charlet@gcc.gnu.org> | 2009-04-10 15:11:14 +0200 |
---|---|---|
committer | Arnaud Charlet <charlet@gcc.gnu.org> | 2009-04-10 15:11:14 +0200 |
commit | 4d2907fdba36553b95a80003fdbadc110b233461 (patch) | |
tree | 1b48a88e7f624d1466aaf27bb186b3312474c85d /gcc/ada/sem_res.adb | |
parent | 3996951a3e5a105d1af6e41c09b1bfda72bd96b7 (diff) | |
download | gcc-4d2907fdba36553b95a80003fdbadc110b233461.zip gcc-4d2907fdba36553b95a80003fdbadc110b233461.tar.gz gcc-4d2907fdba36553b95a80003fdbadc110b233461.tar.bz2 |
Update comments.
From-SVN: r145895
Diffstat (limited to 'gcc/ada/sem_res.adb')
-rw-r--r-- | gcc/ada/sem_res.adb | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/gcc/ada/sem_res.adb b/gcc/ada/sem_res.adb index 0d40e5a..c9356b6 100644 --- a/gcc/ada/sem_res.adb +++ b/gcc/ada/sem_res.adb @@ -5045,20 +5045,20 @@ package body Sem_Res is -- There are several notable exceptions: - -- a) in init procs, the transient scope overhead is not needed, and is + -- a) In init procs, the transient scope overhead is not needed, and is -- even incorrect when the call is a nested initialization call for a -- component whose expansion may generate adjust calls. However, if the -- call is some other procedure call within an initialization procedure -- (for example a call to Create_Task in the init_proc of the task -- run-time record) a transient scope must be created around this call. - -- b) enumeration literal pseudo-calls need no transient scope. + -- b) Enumeration literal pseudo-calls need no transient scope - -- c) intrinsic subprograms (Unchecked_Conversion and source info + -- c) Intrinsic subprograms (Unchecked_Conversion and source info -- functions) do not use the secondary stack even though the return - -- type may be unconstrained; + -- type may be unconstrained. - -- d) calls to a build-in-place function, since such functions may + -- d) Calls to a build-in-place function, since such functions may -- allocate their result directly in a target object, and cases where -- the result does get allocated in the secondary stack are checked for -- within the specialized Exp_Ch6 procedures for expanding those |