| commit | 9cdaa52bf8e0529c3d4d13121c440f92113ff05d | |
| author | Eric Botcazou <ebotcazou@adacore.com> | |
| Tue, 16 May 2023 09:35:23 +0000 (16 11:35 +0200) | ||
| committer | Marc Poulhiès <poulhies@adacore.com> | |
| Thu, 15 Jun 2023 07:59:37 +0000 (15 09:59 +0200) | ||
| tree | c7faa39801a9c16cdccaf50f1687cc1b8cb96d0f | treesnapshot (tar.gz zip) |
| parent | c8c5bf93aaa481d4b08491d4545b74e2b329d16d | commitdiff |
ada: Revert latest change to Find_Hook_Context
The issue is that, if an aggregate is both below a conditional expression
and above another conditional expression in the tree, we have currently no
place to put the finalization actions generated by the innermost expression
in the context of the aggregate before it is expanded, so they end up being
placed after the outermost expression.
But it is not clear whether that's really problematic because this does not
seem to happen for array aggregates with multiple or others choices: in this
case the aggregate is expanded first and the code path is not taken.
gcc/ada/
* exp_util.adb (Find_Hook_Context): Revert latest change.
The issue is that, if an aggregate is both below a conditional expression
and above another conditional expression in the tree, we have currently no
place to put the finalization actions generated by the innermost expression
in the context of the aggregate before it is expanded, so they end up being
placed after the outermost expression.
But it is not clear whether that's really problematic because this does not
seem to happen for array aggregates with multiple or others choices: in this
case the aggregate is expanded first and the code path is not taken.
gcc/ada/
* exp_util.adb (Find_Hook_Context): Revert latest change.
| gcc/ada/exp_util.adb | diffblobblamehistory |