public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <pmderodat@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1515] [Ada] Fix typos in all occurrences of "occuring" in GNAT
Date: Wed, 16 Jun 2021 08:45:39 +0000 (GMT)	[thread overview]
Message-ID: <20210616084539.0582D398A87D@sourceware.org> (raw)

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

commit r12-1515-ge027681d90cee11d082fefb937b0233de81e9e7b
Author: Piotr Trojanek <trojanek@adacore.com>
Date:   Tue Mar 2 09:58:20 2021 +0100

    [Ada] Fix typos in all occurrences of "occuring" in GNAT
    
    gcc/ada/
    
            * restrict.adb, sem_attr.adb, types.ads: Fix typos in
            "occuring"; refill comment as necessary.

Diff:
---
 gcc/ada/restrict.adb | 2 +-
 gcc/ada/sem_attr.adb | 9 +++++----
 gcc/ada/types.ads    | 2 +-
 3 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/gcc/ada/restrict.adb b/gcc/ada/restrict.adb
index 60faa2ac3b8..35922307460 100644
--- a/gcc/ada/restrict.adb
+++ b/gcc/ada/restrict.adb
@@ -66,7 +66,7 @@ package body Restrict is
 
    No_Specification_Of_Aspects : array (Aspect_Id) of Source_Ptr :=
                                    (others => No_Location);
-   --  Entries in this array are set to point to a previously occuring pragma
+   --  Entries in this array are set to point to a previously occurring pragma
    --  that activates a No_Specification_Of_Aspect check.
 
    No_Specification_Of_Aspect_Warning : array (Aspect_Id) of Boolean :=
diff --git a/gcc/ada/sem_attr.adb b/gcc/ada/sem_attr.adb
index 83f53cdf1fb..63b0f09ea5d 100644
--- a/gcc/ada/sem_attr.adb
+++ b/gcc/ada/sem_attr.adb
@@ -10751,10 +10751,11 @@ package body Sem_Attr is
                   Nm : Node_Id;
 
                   Note : Boolean := True;
-                  --  Skip this for the case of Unrestricted_Access occuring in
-                  --  the context of a Valid check, since this otherwise leads
-                  --  to a missed warning (the Valid check does not really
-                  --  modify!) If this case, Note will be reset to False.
+                  --  Skip this for the case of Unrestricted_Access occurring
+                  --  in the context of a Valid check, since this otherwise
+                  --  leads to a missed warning (the Valid check does not
+                  --  really modify!) If this case, Note will be reset to
+                  --  False.
 
                   --  Skip it as well if the type is an Access_To_Constant,
                   --  given that no use of the value can modify the prefix.
diff --git a/gcc/ada/types.ads b/gcc/ada/types.ads
index 27c50efed1c..ef87a5a3e48 100644
--- a/gcc/ada/types.ads
+++ b/gcc/ada/types.ads
@@ -773,7 +773,7 @@ package Types is
       Overflow_Mode_Assertions : Overflow_Mode_Type;
       --  This field indicates the mode for handling code generation and
       --  overflow checking (if enabled) for intermediate expression values.
-      --  This applies to any expression occuring inside assertions.
+      --  This applies to any expression occurring inside assertions.
    end record;
 
    -----------------------------------


                 reply	other threads:[~2021-06-16  8:45 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=20210616084539.0582D398A87D@sourceware.org \
    --to=pmderodat@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).