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 r14-1984] ada: Remove outdated comment
Date: Tue, 20 Jun 2023 11:26:08 +0000 (GMT)	[thread overview]
Message-ID: <20230620112608.A9D323858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:31edd39bc418ccb6b806767ff5cbefd98fb81fb5

commit r14-1984-g31edd39bc418ccb6b806767ff5cbefd98fb81fb5
Author: Ronan Desplanques <desplanques@adacore.com>
Date:   Fri Jun 9 14:31:00 2023 +0200

    ada: Remove outdated comment
    
    The Preelaborate pragma the removed comment was referring to was
    indeed present in AI 167, as well as in clause 5.3 of the rationale
    for Ada 2012, but it never made it into the 2012 version of the
    reference manual.
    
    gcc/ada/
    
            * libgnarl/s-mudido.ads: Remove outdated comment.

Diff:
---
 gcc/ada/libgnarl/s-mudido.ads | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/gcc/ada/libgnarl/s-mudido.ads b/gcc/ada/libgnarl/s-mudido.ads
index 06e48bd1b9c..cc97463077b 100644
--- a/gcc/ada/libgnarl/s-mudido.ads
+++ b/gcc/ada/libgnarl/s-mudido.ads
@@ -20,10 +20,6 @@ with Ada.Task_Identification;
 private with System.Tasking;
 
 package System.Multiprocessors.Dispatching_Domains is
-   --  pragma Preelaborate (Dispatching_Domains);
-   --  ??? According to AI 167 this unit should be preelaborate, but it cannot
-   --  be preelaborate because it depends on Ada.Real_Time which is not
-   --  preelaborate.
 
    Dispatching_Domain_Error : exception;

                 reply	other threads:[~2023-06-20 11:26 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=20230620112608.A9D323858D28@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).