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-3668] ada: Skip dynamic interface conversion under configurable runtime
Date: Fri,  4 Nov 2022 13:54:27 +0000 (GMT)	[thread overview]
Message-ID: <20221104135427.EB9DE3857BA1@sourceware.org> (raw)

https://gcc.gnu.org/g:64b10736a16c901701e4c97ce71504791ba9bbea

commit r13-3668-g64b10736a16c901701e4c97ce71504791ba9bbea
Author: Javier Miranda <miranda@adacore.com>
Date:   Fri Oct 7 16:02:02 2022 +0000

    ada: Skip dynamic interface conversion under configurable runtime
    
    gcc/ada/
    
            * exp_disp.adb
            (Expand_Interface_Conversion): Fix typo in comment.

Diff:
---
 gcc/ada/exp_disp.adb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/ada/exp_disp.adb b/gcc/ada/exp_disp.adb
index d8a45ffb7c9..41da7a23ee5 100644
--- a/gcc/ada/exp_disp.adb
+++ b/gcc/ada/exp_disp.adb
@@ -1308,7 +1308,7 @@ package body Exp_Disp is
          --  When the target type is an interface type that is an ancestor of
          --  the operand type, it is generally safe to skip generating code to
          --  displace the pointer to the object to reference the secondary
-         --  dispatch table of the target interface type. Two scenaries are
+         --  dispatch table of the target interface type. Two scenarios are
          --  possible here:
          --    1) The operand type is a regular tagged type
          --    2) The operand type is an interface type

                 reply	other threads:[~2022-11-04 13:54 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=20221104135427.EB9DE3857BA1@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).