public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Joseph Faulls <Joseph.Faulls@imgtec.com>
Cc: "nelson@rivosinc.com" <nelson@rivosinc.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH] RISC-V: Add support for numbered ISA mapping strings
Date: Wed, 27 Sep 2023 14:09:30 +0200	[thread overview]
Message-ID: <ee9d219a-8d1a-3cfe-a98e-3ccea5d733b0@suse.com> (raw)
In-Reply-To: <LO4P265MB5914E1FBFD4DE046CC1F80E880C2A@LO4P265MB5914.GBRP265.PROD.OUTLOOK.COM>

On 27.09.2023 13:20, Joseph Faulls wrote:
> --- a/opcodes/riscv-dis.c
> +++ b/opcodes/riscv-dis.c
> @@ -869,7 +869,23 @@ riscv_get_map_state (int n,
>      {
>        *state = MAP_INSN;
>        riscv_release_subset_list (&riscv_subsets);
> -      riscv_parse_subset (&riscv_rps_dis, name + 2);
> +
> +      /* ISA mapping string may be numbered, suffixed with '.n'. Do not
> +        consider this as part of the ISA string.  */
> +      char *suffix = strchr (name, '.');
> +      if (suffix)
> +       {
> +         int suffix_index = (int)(suffix - name);
> +         char *name_substr = malloc (suffix_index + 1);
> +         strncpy (name_substr, name, suffix_index);

You want to either use xmalloc(), or you need to check for getting
back NULL here.

Jan

> +         name_substr[suffix_index] = '\0';
> +         riscv_parse_subset (&riscv_rps_dis, name_substr + 2);
> +         free (name_substr);
> +       }
> +      else
> +       {
> +         riscv_parse_subset (&riscv_rps_dis, name + 2);
> +       }
>      }
>    else
>      return false;
> --
> 2.34.1


      reply	other threads:[~2023-09-27 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 11:20 Joseph Faulls
2023-09-27 12:09 ` Jan Beulich [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=ee9d219a-8d1a-3cfe-a98e-3ccea5d733b0@suse.com \
    --to=jbeulich@suse.com \
    --cc=Joseph.Faulls@imgtec.com \
    --cc=binutils@sourceware.org \
    --cc=nelson@rivosinc.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).