From: Jeff Law <jlaw@ventanamicro.com>
Date: Mon, 24 Jul 2023 13:56:36 +0000 (-0600)
Subject: [committed][RISC-V] Fix minor issues in diagnostic message
X-Git-Tag: basepoints/gcc-15~7391
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=aa1e2d543869a07580f9b2112f2d7367f83a6753;p=thirdparty%2Fgcc.git

[committed][RISC-V] Fix minor issues in diagnostic message

This fixes two minor issues with the recently adding warning about too large
VLEN in the RISC-V backend.  These prevent the RISC-V port from bootstrapping
as both Andreas and I have found.

Specifically we'll get warnings for the use of '>' in the recently added
 message as well as using "can not" vs "cannot".  While these warnings may
seem annoying, they're in place to make it easier for the translators.

This patch fixes the message in the fairly obvious way.  Spells out the
greater than and uses cannot.  There's a similar issue in another recently
added diagnostic that I'll push momentarily.

gcc/
	* config/riscv/riscv.cc (riscv_option_override): Spell out
	greater than and use cannot in diagnostic string.
---

diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
index 332fa720f018..941ea25e1f21 100644
--- a/gcc/config/riscv/riscv.cc
+++ b/gcc/config/riscv/riscv.cc
@@ -6713,7 +6713,7 @@ riscv_option_override (void)
      We can only allow TARGET_MIN_VLEN * 8 (LMUL) < 65535.  */
   if (TARGET_MIN_VLEN > 4096)
     sorry (
-      "Current RISC-V GCC can not support VLEN > 4096bit for 'V' Extension");
+      "Current RISC-V GCC cannot support VLEN greater than 4096bit for 'V' Extension");
 
   /* Convert -march to a chunks count.  */
   riscv_vector_chunks = riscv_convert_vector_bits ();