public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Marc Poulhi?s <dkm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3794] ada: Propagate aspect Ghost when instantiating null formal procedures
Date: Tue,  8 Nov 2022 08:41:57 +0000 (GMT)	[thread overview]
Message-ID: <20221108084157.60ABB3858283@sourceware.org> (raw)

https://gcc.gnu.org/g:a645dc3c20c32ede1b5f50f1a35705ce87a3d61b

commit r13-3794-ga645dc3c20c32ede1b5f50f1a35705ce87a3d61b
Author: Piotr Trojanek <trojanek@adacore.com>
Date:   Fri Oct 21 20:12:15 2022 +0200

    ada: Propagate aspect Ghost when instantiating null formal procedures
    
    When instantiating generic package that includes a formal subprogram
    declaration with Ghost aspect and a subprogram_default of null, e.g.:
    
       generic
         with procedure Proc is null with Ghost;
       package P is ...
    
    the Ghost aspect should be propagated to the internally generated null
    subprogram, so this null subprogram can be used in contexts that require
    ghost entities.
    
    gcc/ada/
    
            * sem_ch12.adb (Instantiate_Formal_Subprogram): Copy aspect Ghost
            from formal subprogram declaration to the internally generated
            procedure.

Diff:
---
 gcc/ada/sem_ch12.adb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/ada/sem_ch12.adb b/gcc/ada/sem_ch12.adb
index ca0f4913e36..276656085be 100644
--- a/gcc/ada/sem_ch12.adb
+++ b/gcc/ada/sem_ch12.adb
@@ -11088,6 +11088,8 @@ package body Sem_Ch12 is
 
          Set_Convention (Defining_Unit_Name (New_Spec), Convention_Intrinsic);
 
+         Copy_Ghost_Aspect (Formal, To => Decl_Node);
+
          --  Eliminate the calls to it when optimization is enabled
 
          Set_Is_Inlined (Defining_Unit_Name (New_Spec));

                 reply	other threads:[~2022-11-08  8:41 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=20221108084157.60ABB3858283@sourceware.org \
    --to=dkm@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: link
Be 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).