public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <pmderodat@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1472] [Ada] Fix handling of scopes for subprogram calls in unnesting Date: Tue, 15 Jun 2021 10:22:33 +0000 (GMT) [thread overview] Message-ID: <20210615102233.6FE7E383D03C@sourceware.org> (raw) https://gcc.gnu.org/g:4cee20bb1ebbe66d4065c33da9f8743683228ede commit r12-1472-g4cee20bb1ebbe66d4065c33da9f8743683228ede Author: Arnaud Charlet <charlet@adacore.com> Date: Thu Feb 11 14:08:35 2021 +0100 [Ada] Fix handling of scopes for subprogram calls in unnesting gcc/ada/ * exp_unst.adb (Unnest_Subprogram.Build_Table.Visit_Node): Fix handling of scopes for subprogram calls. Diff: --- gcc/ada/exp_unst.adb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/ada/exp_unst.adb b/gcc/ada/exp_unst.adb index 6fd7a0ec6b9..52d6142f20d 100644 --- a/gcc/ada/exp_unst.adb +++ b/gcc/ada/exp_unst.adb @@ -883,7 +883,7 @@ package body Exp_Unst is -- within Subp. Calls to Subp itself or to subprograms -- outside the nested structure do not affect us. - if Scope_Within (Ent, Subp) + if Scope_Within (Ultimate_Alias (Ent), Subp) and then Is_Subprogram (Ent) and then not Is_Imported (Ent) then
reply other threads:[~2021-06-15 10:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210615102233.6FE7E383D03C@sourceware.org \ --to=pmderodat@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).