From: rep.dot.nop@gmail.com
To: Kito Cheng <kito.cheng@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: "Kito.cheng" <kito.cheng@sifive.com>,
jeffreyalaw <jeffreyalaw@gmail.com>,
Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] RISC-V: Tweak the wording for the sorry message
Date: Fri, 19 Jan 2024 10:40:26 +0100 [thread overview]
Message-ID: <30359D73-87EE-45B5-A232-AF4AC011E481@gmail.com> (raw)
In-Reply-To: <CA+yXCZBSAHfU5rt=K2P1SviDPbnwuLXEmdB+7G7xhmENm-W7GQ@mail.gmail.com>
On 19 January 2024 03:41:57 CET, Kito Cheng <kito.cheng@gmail.com> wrote:
>Thanks, pushed to trunk :)
Thanks, but don't you have to update the tests too, at least
gcc/testsuite/gcc.target/riscv/rvv/base/big_endian-2.c ?
thanks
>
>On Fri, Jan 19, 2024 at 10:36 AM juzhe.zhong@rivai.ai
><juzhe.zhong@rivai.ai> wrote:
>>
>> OK
>>
>> ________________________________
>> juzhe.zhong@rivai.ai
>>
>>
>> From: Kito Cheng
>> Date: 2024-01-19 10:34
>> To: rep.dot.nop; jeffreyalaw; rdapp.gcc; juzhe.zhong; gcc-patches
>> CC: Kito Cheng
>> Subject: [PATCH] RISC-V: Tweak the wording for the sorry message
>> Use "does not" rather than "cannot", because it's implementation issue.
>>
>> gcc/ChangeLog:
>>
>> * config/riscv/riscv.cc (riscv_override_options_internal): Tweak
>> sorry message.
>> ---
>> gcc/config/riscv/riscv.cc | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
>> index f1d5129397f..dd6e68a08c2 100644
>> --- a/gcc/config/riscv/riscv.cc
>> +++ b/gcc/config/riscv/riscv.cc
>> @@ -8798,13 +8798,13 @@ riscv_override_options_internal (struct gcc_options *opts)
>> We can only allow TARGET_MIN_VLEN * 8 (LMUL) < 65535. */
>> if (TARGET_MIN_VLEN_OPTS (opts) > 4096)
>> - sorry ("Current RISC-V GCC cannot support VLEN greater than 4096bit for "
>> + sorry ("Current RISC-V GCC does not support VLEN greater than 4096bit for "
>> "'V' Extension");
>> /* FIXME: We don't support RVV in big-endian for now, we may enable RVV with
>> big-endian after finishing full coverage testing. */
>> if (TARGET_VECTOR && TARGET_BIG_ENDIAN)
>> - sorry ("Current RISC-V GCC cannot support RVV in big-endian mode");
>> + sorry ("Current RISC-V GCC does not support RVV in big-endian mode");
>> /* Convert -march to a chunks count. */
>> riscv_vector_chunks = riscv_convert_vector_bits (opts);
>> --
>> 2.34.1
>>
>>
next prev parent reply other threads:[~2024-01-19 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 2:34 Kito Cheng
2024-01-19 2:35 ` juzhe.zhong
2024-01-19 2:41 ` Kito Cheng
2024-01-19 9:40 ` rep.dot.nop [this message]
2024-01-19 9:43 ` juzhe.zhong
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=30359D73-87EE-45B5-A232-AF4AC011E481@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=rdapp.gcc@gmail.com \
/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).