summaryrefslogtreecommitdiff
path: root/gcc/ada/exp_ch6.adb
diff options
context:
space:
mode:
authorcharlet <charlet@138bc75d-0d04-0410-961f-82ee72b054a4>2014-08-04 12:53:23 +0000
committercharlet <charlet@138bc75d-0d04-0410-961f-82ee72b054a4>2014-08-04 12:53:23 +0000
commitdae843bcc0b0aba643fa49b116cc22580242b2d6 (patch)
tree6da8c2645ef62d60d2561f874976f2d90c895f8f /gcc/ada/exp_ch6.adb
parenta52fe7b10e5661513e99a0577b024644f4951be6 (diff)
downloadgcc-dae843bcc0b0aba643fa49b116cc22580242b2d6.tar.gz
2014-08-04 Olivier Hainque <hainque@adacore.com>
* a-comutr.ads: Set Root_Node_Type'Alignment to Standard'Maximum_Alignment, so that it is at least as large as the max default for Tree_Node_Type'Alignment. 2014-08-04 Hristian Kirtchev <kirtchev@adacore.com> * exp_ch3.adb (Freeze_Type): Remove the generation and inheritance of the default initial condition procedure [body]. * sem_ch3.adb (Analyze_Declarations): Create the bodies of all default initial condition procedures at the end of private declaration analysis. * sem_util.adb (Build_Default_Init_Cond_Procedure_Bodies): New routine. (Build_Default_Init_Cond_Procedure_Body): Merged in the processing of routine Build_Default_Init_Cond_Procedure_Bodies. * sem_util.ads (Build_Default_Init_Cond_Procedure_Bodies): New routine. (Build_Default_Init_Cond_Procedure_Body): Removed. 2014-08-04 Ed Schonberg <schonberg@adacore.com> * sem_elab.adb (Check_Elab_Call): Do not check a call to a postcondtion. * exp_ch6.adb (Expand_Call): Clarify handling of inserted postcondition call. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@213580 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/ada/exp_ch6.adb')
-rw-r--r--gcc/ada/exp_ch6.adb7
1 files changed, 7 insertions, 0 deletions
diff --git a/gcc/ada/exp_ch6.adb b/gcc/ada/exp_ch6.adb
index 7f111901b05..82c87871f87 100644
--- a/gcc/ada/exp_ch6.adb
+++ b/gcc/ada/exp_ch6.adb
@@ -5209,6 +5209,13 @@ package body Exp_Ch6 is
-- Analyze call, but something goes wrong in some weird cases
-- and it is not worth worrying about ???
+ -- The return statement is handled properly, and the call to
+ -- the postcondition, inserted below, does not require
+ -- information from the body either. However, that call is
+ -- analyzed in the enclosing scope, and an elaboration check
+ -- might improperly be added to it. A guard in sem_elab is
+ -- needed to prevent that spurious check, see Check_Elab_Call.
+
Append_To (S, Rtn);
Set_Analyzed (Rtn);