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 r13-602] [Ada] Use specific predicate before manipulating BIP_Alloc_Form Date: Wed, 18 May 2022 08:44:23 +0000 (GMT) [thread overview] Message-ID: <20220518084423.89AAB3857413@sourceware.org> (raw) https://gcc.gnu.org/g:ef07419f73ac5cc436282a607591e289bb480626 commit r13-602-gef07419f73ac5cc436282a607591e289bb480626 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Mon Mar 28 21:16:24 2022 +0200 [Ada] Use specific predicate before manipulating BIP_Alloc_Form For the sake of consistency with other similar manipulations. gcc/ada/ * exp_ch7.adb (Build_BIP_Cleanup_Stmts): Use Needs_BIP_Alloc_Form. Diff: --- gcc/ada/exp_ch7.adb | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/gcc/ada/exp_ch7.adb b/gcc/ada/exp_ch7.adb index 74343646515..0c53f326887 100644 --- a/gcc/ada/exp_ch7.adb +++ b/gcc/ada/exp_ch7.adb @@ -2850,16 +2850,14 @@ package body Exp_Ch7 is Left_Opnd => New_Occurrence_Of (Fin_Mas_Id, Loc), Right_Opnd => Make_Null (Loc)); - -- For constrained or tagged results escalate the condition to + -- For unconstrained or tagged results, escalate the condition to -- include the allocation format. Generate: -- if BIPallocform > Secondary_Stack'Pos -- and then BIPfinalizationmaster /= null -- then - if not Is_Constrained (Func_Typ) - or else Is_Tagged_Type (Func_Typ) - then + if Needs_BIP_Alloc_Form (Func_Id) then declare Alloc : constant Entity_Id := Build_In_Place_Formal (Func_Id, BIP_Alloc_Form);
reply other threads:[~2022-05-18 8:44 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=20220518084423.89AAB3857413@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).