From: Jan Beulich <jbeulich@suse.com>
To: Li Xu <xuli1@eswincomputing.com>
Cc: kito.cheng@gmail.com, palmer@dabbelt.com, binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Warn in AS if vsew/vlmul/vtype is reserved.
Date: Fri, 19 May 2023 08:21:54 +0200 [thread overview]
Message-ID: <ee50f3f8-44ba-c425-4b92-2eebddcf0532@suse.com> (raw)
In-Reply-To: <20230518065950.6166-1-xuli1@eswincomputing.com>
On 18.05.2023 08:59, Li Xu wrote:
> Consider the following case:
>
> vsetvli a0, a1, 0x4 # unrecognized vlmul
> vsetvli a0, a1, 0x20 # unrecognized vsew
> vsetvli a0, a1, 0x700 # unrecognized vtype
>
> The current AS doesn't have any hints, so I think
> it's better to give a warning.
>
> After this patch:
> test.s: Assembler messages:
> test.s:1: Warning: The vtype encoding of vlmul = 0x4 is reserved.
> test.s:2: Warning: The vtype encoding of vsew = 0x4 is reserved.
> test.s:3: Warning: The vtype encoding of 0x700 is reserved.
But then I think there wants to be a way to silence these warnings,
which may be of interest if any of the presently reserved values
gains a meaning.
Jan
next prev parent reply other threads:[~2023-05-19 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 6:59 Li Xu
2023-05-19 6:21 ` Jan Beulich [this message]
2023-05-19 2:14 Li Xu
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=ee50f3f8-44ba-c425-4b92-2eebddcf0532@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=xuli1@eswincomputing.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).