public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Marc Poulhiès" <poulhies@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Ronan Desplanques <desplanques@adacore.com>
Subject: [COMMITTED] ada: Fix minor issues in comments
Date: Thu, 15 Jun 2023 10:04:02 +0200	[thread overview]
Message-ID: <20230615080402.939162-1-poulhies@adacore.com> (raw)

From: Ronan Desplanques <desplanques@adacore.com>

The package Ttypef has been removed but a reference to it was left
over in a comment. This patch removes that reference, and also fixes
a typo.

gcc/ada/

	* ttypes.ads: Remove reference to Ttypef in comment. Fix typo in
	comment.

Tested on x86_64-pc-linux-gnu, committed on master.

---
 gcc/ada/ttypes.ads | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/gcc/ada/ttypes.ads b/gcc/ada/ttypes.ads
index c8188ea9f98..28c63769d96 100644
--- a/gcc/ada/ttypes.ads
+++ b/gcc/ada/ttypes.ads
@@ -60,11 +60,10 @@ package Ttypes is
    --  Two approaches are used for handling target dependent values in the
    --  standard library packages. Package Standard is handled specially,
    --  being constructed internally (by package Stand). Target dependent
-   --  values needed in Stand are obtained by direct reference to Ttypes
-   --  and Ttypef.
+   --  values needed in Stand are obtained by direct reference to Ttypes.
 
    --  For package System, there is a separate version for each target, with
-   --  explicit declarations of the required, constants.
+   --  explicit declarations of the required constants.
 
    --  Historical note: Originally we had in mind dealing with target dependent
    --  differences by referencing appropriate attributes. Ada 95 already
-- 
2.40.0


                 reply	other threads:[~2023-06-15  8:04 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=20230615080402.939162-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).