From: Nelson Chu <nelson@rivosinc.com>
To: Joseph Faulls <Joseph.Faulls@imgtec.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
"jbeulich@suse.com" <jbeulich@suse.com>
Subject: Re: [PATCH v2] RISC-V: Add support for numbered ISA mapping strings
Date: Thu, 28 Sep 2023 09:41:08 +0800 [thread overview]
Message-ID: <CAPpQWtAxdKt-WmYgsDF1abAZFS87p2cqsU6w3FSb1jy5613=VQ@mail.gmail.com> (raw)
In-Reply-To: <LO4P265MB591487CCBB57E75FE05F23AF80C2A@LO4P265MB5914.GBRP265.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
Okay, although the current GNU assembler won't generate numbered
architecture strings, other tools may generate, so this looks reasonable.
Thanks
Nelson
On Wed, Sep 27, 2023 at 8:42 PM Joseph Faulls <Joseph.Faulls@imgtec.com>
wrote:
> The elf psabi allows for mapping symbols to be of the form $x<ISA>.<any>
>
>
>
> opcodes/
>
> * riscv-dis.c (riscv_get_map_state): allow mapping symbol to
>
> be suffixed by a unique identifier .<any>
>
>
>
> Changes from v1:
>
> - Use xmalloc (thanks Jan)
>
> ---
>
> opcodes/riscv-dis.c | 18 +++++++++++++++++-
>
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
>
>
> diff --git a/opcodes/riscv-dis.c b/opcodes/riscv-dis.c
>
> index c0fd0625a2d..18a5c26f9a6 100644
>
> --- 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 = xmalloc (suffix_index + 1);
>
> + strncpy (name_substr, name, suffix_index);
>
> + 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
>
next prev parent reply other threads:[~2023-09-28 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:42 Joseph Faulls
2023-09-28 1:41 ` Nelson Chu [this message]
2023-10-12 15:46 ` [EXTERNAL] " Joseph Faulls
2023-10-13 1:57 ` Nelson Chu
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='CAPpQWtAxdKt-WmYgsDF1abAZFS87p2cqsU6w3FSb1jy5613=VQ@mail.gmail.com' \
--to=nelson@rivosinc.com \
--cc=Joseph.Faulls@imgtec.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).