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-844] [Ada] Fix Warn_On_All_Unread_Out_Parameters not being properly tagged
Date: Mon, 30 May 2022 08:31:28 +0000 (GMT)	[thread overview]
Message-ID: <20220530083128.82C253815FEE@sourceware.org> (raw)

https://gcc.gnu.org/g:67481ef52716c9baa0d69b7ce54f935e50982a11

commit r13-844-g67481ef52716c9baa0d69b7ce54f935e50982a11
Author: Ghjuvan Lacambre <lacambre@adacore.com>
Date:   Tue Apr 26 09:32:59 2022 +0200

    [Ada] Fix Warn_On_All_Unread_Out_Parameters not being properly tagged
    
    This caused tools ingesting GNAT's output to mislabel these messages.
    
    gcc/ada/
    
            * sem_warn.adb (Warn_On_Useless_Assignment): Fix insertion
            character.

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

diff --git a/gcc/ada/sem_warn.adb b/gcc/ada/sem_warn.adb
index 1bc248ce00e..251235797e9 100644
--- a/gcc/ada/sem_warn.adb
+++ b/gcc/ada/sem_warn.adb
@@ -4595,7 +4595,7 @@ package body Sem_Warn is
                         then
                            if Warn_On_All_Unread_Out_Parameters then
                               Error_Msg_NE
-                                ("?m?& modified by call, but value might not "
+                                ("?.o?& modified by call, but value might not "
                                  & "be referenced", LA, Ent);
                            end if;
                         else


                 reply	other threads:[~2022-05-30  8:31 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=20220530083128.82C253815FEE@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).