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 r13-225] [Ada] Fix comment about building names in task arrays
Date: Tue, 10 May 2022 08:20:50 +0000 (GMT)	[thread overview]
Message-ID: <20220510082050.D36A6388703B@sourceware.org> (raw)

https://gcc.gnu.org/g:3d9e2004fe4e15b133bd8472c4bf46cbff809583

commit r13-225-g3d9e2004fe4e15b133bd8472c4bf46cbff809583
Author: Piotr Trojanek <trojanek@adacore.com>
Date:   Wed Jan 19 13:29:46 2022 +0100

    [Ada] Fix comment about building names in task arrays
    
    Cleanup related to handling of character values in SPARK
    counterexamples, which just like the code for names in task arrays
    create N_Character_Literal nodes.
    
    gcc/ada/
    
            * exp_util.adb (Build_Task_Array_Image): Fix style in the
            structure of generated code; add Pref'Length as the component of
            the Sum initialization expression.

Diff:
---
 gcc/ada/exp_util.adb | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/gcc/ada/exp_util.adb b/gcc/ada/exp_util.adb
index 263b42f7586..b3d1fdf3cdf 100644
--- a/gcc/ada/exp_util.adb
+++ b/gcc/ada/exp_util.adb
@@ -4048,13 +4048,13 @@ package body Exp_Util is
    --  The generated function has the following structure:
 
    --  function F return String is
-   --     Pref : string renames Task_Name;
+   --     Pref : String renames Task_Name;
    --     T1   : String := Index1'Image (Val1);
    --     ...
-   --     Tn   : String := indexn'image (Valn);
-   --     Len  : Integer := T1'Length + ... + Tn'Length + n + 1;
-   --     --  Len includes commas and the end parentheses.
-   --     Res  : String (1..Len);
+   --     Tn   : String := Indexn'Image (Valn);
+   --     Len  : Integer := Pref'Length + T1'Length + ... + Tn'Length + n + 1;
+   --     --  Len includes commas and the end parentheses
+   --     Res  : String (1 .. Len);
    --     Pos  : Integer := Pref'Length;
    --
    --  begin


                 reply	other threads:[~2022-05-10  8:20 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=20220510082050.D36A6388703B@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).