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-4234] ada: Accept aspects Global and Depends on abstract subprograms
Date: Tue, 22 Nov 2022 12:36:15 +0000 (GMT)	[thread overview]
Message-ID: <20221122123615.01EDC38582AB@sourceware.org> (raw)

https://gcc.gnu.org/g:61351ab96a4dfa0884c8b1a53342b97915fb5dd7

commit r13-4234-g61351ab96a4dfa0884c8b1a53342b97915fb5dd7
Author: Piotr Trojanek <trojanek@adacore.com>
Date:   Mon Nov 21 11:31:29 2022 +0100

    ada: Accept aspects Global and Depends on abstract subprograms
    
    Aspects Global and Depends are now allowed on abstract subprograms
    (as substitutes for Global'Class and Depends'Class).
    
    This patch implements the recently modified rules SPARK RM 6.1.2(2-3).
    The behavior for Contract_Cases and aspects on null subprograms stays
    as it was.
    
    gcc/ada/
    
            * sem_prag.adb (Analyze_Depends_Global): Accept aspects on
            abstract subprograms.

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

diff --git a/gcc/ada/sem_prag.adb b/gcc/ada/sem_prag.adb
index f2c1a3f0e6e..0a91518cff9 100644
--- a/gcc/ada/sem_prag.adb
+++ b/gcc/ada/sem_prag.adb
@@ -4549,6 +4549,11 @@ package body Sem_Prag is
          elsif Nkind (Subp_Decl) = N_Single_Task_Declaration then
             null;
 
+         --  Abstract subprogram declaration
+
+         elsif Nkind (Subp_Decl) = N_Abstract_Subprogram_Declaration then
+            null;
+
          --  Subprogram body acts as spec
 
          elsif Nkind (Subp_Decl) = N_Subprogram_Body

                 reply	other threads:[~2022-11-22 12:36 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=20221122123615.01EDC38582AB@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).