public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4597] fortran/openmp.cc: Remove 's' that slipped in during %<..%> replacement
Date: Sun, 11 Dec 2022 10:55:34 +0000 (GMT)	[thread overview]
Message-ID: <20221211105534.56F5C388C5DF@sourceware.org> (raw)

https://gcc.gnu.org/g:045592f665bcb67b75dc6b86badbe2fd44aed3e6

commit r13-4597-g045592f665bcb67b75dc6b86badbe2fd44aed3e6
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.

Diff:
---
 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 10:55 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=20221211105534.56F5C388C5DF@sourceware.org \
    --to=burnus@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).