From: Jeff Law <jeffreyalaw@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed] Use single quote rather than backquote in RISC-V diagnostic
Date: Mon, 24 Jul 2023 08:14:37 -0600 [thread overview]
Message-ID: <7ab38962-3068-cb94-f6b9-4331c7916898@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
Similar to the other patch this morning, this fixes a warning that was
causing the RISC-V bootstrap to fail.
In this case the diagnostic used a backquote. This changes it to a
simple single quote which the diagnostic framework won't complain about.
Committed to the trunk.
Jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 2012 bytes --]
commit d90e81af8052e96ae3262ed3ac42682537fc42c6
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Mon Jul 24 08:10:21 2023 -0600
[committed] Use single quote rather than backquote in RISC-V diagnostic
Similar to the other patch this morning, this fixes a warning that was causing
the RISC-V bootstrap to fail.
In this case the diagnostic used a backquote. This changes it to a simple
single quote which the diagnostic framework won't complain about.
Committed to the trunk.
gcc/
* common/config/riscv/riscv-common.cc (riscv_subset_list::add): Use
single quote rather than backquote in diagnostic.
diff --git a/gcc/common/config/riscv/riscv-common.cc b/gcc/common/config/riscv/riscv-common.cc
index 884d81c12aa..5238877a82d 100644
--- a/gcc/common/config/riscv/riscv-common.cc
+++ b/gcc/common/config/riscv/riscv-common.cc
@@ -573,7 +573,7 @@ riscv_subset_list::add (const char *subset, int major_version,
else if (subset[0] == 'z' && !standard_extensions_p (subset))
{
error_at (m_loc,
- "%<-march=%s%>: extension %qs starts with `z` but is "
+ "%<-march=%s%>: extension %qs starts with 'z' but is "
"unsupported standard extension",
m_arch, subset);
return;
@@ -581,7 +581,7 @@ riscv_subset_list::add (const char *subset, int major_version,
else if (subset[0] == 's' && !standard_extensions_p (subset))
{
error_at (m_loc,
- "%<-march=%s%>: extension %qs starts with `s` but is "
+ "%<-march=%s%>: extension %qs starts with 's' but is "
"unsupported standard supervisor extension",
m_arch, subset);
return;
@@ -589,7 +589,7 @@ riscv_subset_list::add (const char *subset, int major_version,
else if (subset[0] == 'x' && !standard_extensions_p (subset))
{
error_at (m_loc,
- "%<-march=%s%>: extension %qs starts with `x` but is "
+ "%<-march=%s%>: extension %qs starts with 'x' but is "
"unsupported non-standard extension",
m_arch, subset);
return;
reply other threads:[~2023-07-24 14:14 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=7ab38962-3068-cb94-f6b9-4331c7916898@gmail.com \
--to=jeffreyalaw@gmail.com \
--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).