public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: [committed] fortran/openmp.cc: Remove 's' that slipped in during %<..%> replacement (was: [Patch] Fortran: Replace simple '.' quotes by %<.%>)
Date: Sun, 11 Dec 2022 12:03:21 +0100	[thread overview]
Message-ID: <d1e2eb80-e4bb-0fa7-f3f3-3b17f6a8a885@codesourcery.com> (raw)
In-Reply-To: <091af345-e484-7cca-e7df-b31bffbbe293@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

On 09.12.22 22:12, Tobias Burnus wrote:
> Found when working on the just submitted/committed patch.

Committed as r13-4590 –  but it required a follow-up that I somehow
missed :-/ but that is now committed as well (as r13-4597).

Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 1179 bytes --]

commit 045592f665bcb67b75dc6b86badbe2fd44aed3e6
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Sun Dec 11 11:47:55 2022 +0100

    fortran/openmp.cc: Remove 's' that slipped in during %<..%> replacement
    
    Seemingly, 's' (in VI that's the 's'ubstitute command) appeared verbatim in
    a gfc_error message when to doing the '...' to %<...%> replacements in commit
    r13-4590-g84f6f8a2a97f88be01e223c9c9dbab801a4f501f
    
    gcc/fortran/
            * openmp.cc (gfc_match_omp_context_selector_specification):
            Remove spurious 's' in an error message.
---
 gcc/fortran/openmp.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/fortran/openmp.cc b/gcc/fortran/openmp.cc
index 7edc78ad0cb..686f924b47a 100644
--- a/gcc/fortran/openmp.cc
+++ b/gcc/fortran/openmp.cc
@@ -5568,7 +5568,7 @@ gfc_match_omp_context_selector_specification (gfc_omp_declare_variant *odv)
 
       if (m != MATCH_YES || i == selector_set_count)
 	{
-	  gfc_error ("expected %<constructs%>, %<device%>, %<implementation%> "
+	  gfc_error ("expected %<construct%>, %<device%>, %<implementation%> "
 		     "or %<user%> at %C");
 	  return MATCH_ERROR;
 	}

      reply	other threads:[~2022-12-11 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 21:12 [Patch] Fortran: Replace simple '.' quotes by %<.%> Tobias Burnus
2022-12-11 11:03 ` Tobias Burnus [this message]

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=d1e2eb80-e4bb-0fa7-f3f3-3b17f6a8a885@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).