public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: Li Xu <xuli1@eswincomputing.com>
Cc: binutils@sourceware.org, kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH v2] RISC-V: Add string length check for operands in AS
Date: Wed, 14 Dec 2022 17:26:05 +0800	[thread overview]
Message-ID: <CAPpQWtARd-fZ2512eQuy+4kkfHhND76C-mNcWbLHhWehYQiAog@mail.gmail.com> (raw)
In-Reply-To: <20221214073240.24973-1-xuli1@eswincomputing.com>

Looks reasonable so committed with passing binutils testsuites.

On Wed, Dec 14, 2022 at 3:33 PM Li Xu <xuli1@eswincomputing.com> wrote:
>
> The patch I previously submitted:
> | Date: Tue Dec 13 04:34:28 GMT 2022
> | Subject: [PATCH] RISC-V: Add string length check for operands in AS
> | Message-ID: <xuli1@eswincomputing.com>
>
> The current AS accepts invalid operands due to miss of operands length check.
> For example, "e6" is an invalid operand in (vsetvli a0, a1, e6, mf8, tu, ma),
> but it's still accepted by assembler. In detail, the condition check "strncmp
> (array[i], *s, len) == 0" in arg_lookup function passes with "strncmp ("e64",
> "e6", 2)" in the case above. So the generated encoding is same as that of
> (vsetvli a0, a1, e64, mf8, tu, ma).
> This patch fixes issue above by prompting an error in such case and also adds
> a new testcase.
>
> gas/ChangeLog:
>
>         * config/tc-riscv.c (arg_lookup): Add string length check for operands.
>         * testsuite/gas/riscv/vector-insns-fail-vsew.d: New testcase for an illegal vsew.
>         * testsuite/gas/riscv/vector-insns-fail-vsew.l: Likewise.
>         * testsuite/gas/riscv/vector-insns-fail-vsew.s: Likewise.
> ---
>  gas/config/tc-riscv.c                            | 3 ++-
>  gas/testsuite/gas/riscv/vector-insns-fail-vsew.d | 3 +++
>  gas/testsuite/gas/riscv/vector-insns-fail-vsew.l | 3 +++
>  gas/testsuite/gas/riscv/vector-insns-fail-vsew.s | 1 +
>  4 files changed, 9 insertions(+), 1 deletion(-)
>  create mode 100644 gas/testsuite/gas/riscv/vector-insns-fail-vsew.d
>  create mode 100644 gas/testsuite/gas/riscv/vector-insns-fail-vsew.l
>  create mode 100644 gas/testsuite/gas/riscv/vector-insns-fail-vsew.s
>
> diff --git a/gas/config/tc-riscv.c b/gas/config/tc-riscv.c
> index 0682eb35524..42c041155c5 100644
> --- a/gas/config/tc-riscv.c
> +++ b/gas/config/tc-riscv.c
> @@ -1206,7 +1206,8 @@ arg_lookup (char **s, const char *const *array, size_t size, unsigned *regnop)
>      return false;
>
>    for (i = 0; i < size; i++)
> -    if (array[i] != NULL && strncmp (array[i], *s, len) == 0)
> +    if (array[i] != NULL && strncmp (array[i], *s, len) == 0
> +        && array[i][len] == '\0')

It is minor that 8 spaces should be replaced by a tab.  Otherwise it looks good.

Thanks
Nelson

>        {
>         *regnop = i;
>         *s += len;
> diff --git a/gas/testsuite/gas/riscv/vector-insns-fail-vsew.d b/gas/testsuite/gas/riscv/vector-insns-fail-vsew.d
> new file mode 100644
> index 00000000000..c0c81579741
> --- /dev/null
> +++ b/gas/testsuite/gas/riscv/vector-insns-fail-vsew.d
> @@ -0,0 +1,3 @@
> +#as: -march=rv32ifv
> +#source: vector-insns-fail-vsew.s
> +#error_output: vector-insns-fail-vsew.l
> diff --git a/gas/testsuite/gas/riscv/vector-insns-fail-vsew.l b/gas/testsuite/gas/riscv/vector-insns-fail-vsew.l
> new file mode 100644
> index 00000000000..87a2c22a805
> --- /dev/null
> +++ b/gas/testsuite/gas/riscv/vector-insns-fail-vsew.l
> @@ -0,0 +1,3 @@
> +.*: Assembler messages:
> +.*: Error: instruction vsetvli requires absolute expression
> +.*: Error: illegal operands `vsetvli a0,a1,e6,mf8,tu,ma'
> diff --git a/gas/testsuite/gas/riscv/vector-insns-fail-vsew.s b/gas/testsuite/gas/riscv/vector-insns-fail-vsew.s
> new file mode 100644
> index 00000000000..b8f3242406f
> --- /dev/null
> +++ b/gas/testsuite/gas/riscv/vector-insns-fail-vsew.s
> @@ -0,0 +1 @@
> +       vsetvli  a0, a1, e6, mf8, tu, ma                # unrecognized vsew
> --
> 2.17.1
>

      reply	other threads:[~2022-12-14  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  7:32 Li Xu
2022-12-14  9:26 ` Nelson Chu [this message]

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=CAPpQWtARd-fZ2512eQuy+4kkfHhND76C-mNcWbLHhWehYQiAog@mail.gmail.com \
    --to=nelson@rivosinc.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).