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-846] [Ada] Add insertion character to Ineffective_Inline_Warnings messages
Date: Mon, 30 May 2022 08:31:38 +0000 (GMT)	[thread overview]
Message-ID: <20220530083138.BAD253815FE6@sourceware.org> (raw)

https://gcc.gnu.org/g:9baae5692bd594024e3131589b8b1e1bfb6e77c1

commit r13-846-g9baae5692bd594024e3131589b8b1e1bfb6e77c1
Author: Ghjuvan Lacambre <lacambre@adacore.com>
Date:   Tue Apr 26 09:55:04 2022 +0200

    [Ada] Add insertion character to Ineffective_Inline_Warnings messages
    
    This enables tools that ingest GNAT's output to properly classify these
    messages.
    
    gcc/ada/
    
            * inline.adb (Check_Package_Body_For_Inlining): Add insertion
            character.

Diff:
---
 gcc/ada/inline.adb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/ada/inline.adb b/gcc/ada/inline.adb
index cc10c2933e4..00c1e033030 100644
--- a/gcc/ada/inline.adb
+++ b/gcc/ada/inline.adb
@@ -2804,8 +2804,8 @@ package body Inline is
                   elsif Ineffective_Inline_Warnings then
                      Error_Msg_Unit_1 := Bname;
                      Error_Msg_N
-                       ("unable to inline subprograms defined in $??", P);
-                     Error_Msg_N ("\body not found??", P);
+                       ("unable to inline subprograms defined in $?p?", P);
+                     Error_Msg_N ("\body not found?p?", P);
                      return;
                   end if;
                end if;


                 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=20220530083138.BAD253815FE6@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).