From: "Marc Poulhiès" <poulhies@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Ronan Desplanques <desplanques@adacore.com>
Subject: [COMMITED] ada: Remove duplicated doc comment section
Date: Thu, 29 Sep 2022 11:11:19 +0200 [thread overview]
Message-ID: <20220929091119.359856-1-poulhies@adacore.com> (raw)
From: Ronan Desplanques <desplanques@adacore.com>
A documentation section was duplicated by mistake in r0-110752.
This commit removes the copy that was added by r0-110752, but
integrates the small editorial change that it brought to the
original.
gcc/ada/
* einfo.ads: remove documentation duplicate
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/einfo.ads | 40 +++-------------------------------------
1 file changed, 3 insertions(+), 37 deletions(-)
diff --git a/gcc/ada/einfo.ads b/gcc/ada/einfo.ads
index 7ac8cf6e99a..e350f137ee7 100644
--- a/gcc/ada/einfo.ads
+++ b/gcc/ada/einfo.ads
@@ -222,10 +222,9 @@ package Einfo is
-- on the actions triggered by a freeze node, which include the construction
-- of initialization procedures and dispatch tables.
--- b) The presence of a freeze node on an entity is used by the back end to
--- defer elaboration of the entity until its freeze node is seen. In the
--- absence of an explicit freeze node, an entity is frozen (and elaborated)
--- at the point of declaration.
+-- b) The flag is used by the back end to defer elaboration of the entity
+-- until its freeze node is seen. In the absence of an explicit freeze node,
+-- an entity is frozen (and elaborated) at the point of declaration.
-- For object declarations, the flag is set when an address clause for the
-- object is encountered. Legality checks on the address expression only take
@@ -4825,39 +4824,6 @@ package Einfo is
-- The front-end does not store explicitly the fact that Z renames X.
---------------------------------------
--- Delayed Freezing and Elaboration --
---------------------------------------
-
--- The flag Has_Delayed_Freeze indicates that an entity carries an explicit
--- freeze node, which appears later in the expanded tree.
-
--- a) The flag is used by the front-end to trigger expansion actions
--- which include the generation of that freeze node. Typically this happens at
--- the end of the current compilation unit, or before the first subprogram
--- body is encountered in the current unit. See files freeze and exp_ch13 for
--- details on the actions triggered by a freeze node, which include the
--- construction of initialization procedures and dispatch tables.
-
--- b) The flag is used by the backend to defer elaboration of the entity until
--- its freeze node is seen. In the absence of an explicit freeze node, an
--- entity is frozen (and elaborated) at the point of declaration.
-
--- For object declarations, the flag is set when an address clause for the
--- object is encountered. Legality checks on the address expression only
--- take place at the freeze point of the object.
-
--- Most types have an explicit freeze node, because they cannot be elaborated
--- until all representation and operational items that apply to them have been
--- analyzed. Private types and incomplete types have the flag set as well, as
--- do task and protected types.
-
--- Implicit base types created for type derivations, as well as classwide
--- types created for all tagged types, have the flag set.
-
--- If a subprogram has an access parameter whose designated type is incomplete
--- the subprogram has the flag set.
-
------------------
-- Access Kinds --
------------------
--
2.25.1
reply other threads:[~2022-09-29 9:11 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=20220929091119.359856-1-poulhies@adacore.com \
--to=poulhies@adacore.com \
--cc=desplanques@adacore.com \
--cc=gcc-patches@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).