public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson.chu@sifive.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Use `xlen' on ADDIW address sequence
Date: Sat, 30 Jul 2022 13:19:06 +0900	[thread overview]
Message-ID: <23f34a05-e0a4-5eb6-fa0b-3555f6ce60e7@irq.a4lg.com> (raw)
In-Reply-To: <448fe9de32d179e3f555587e67352ee677c93747.1657684257.git.research_trasio@irq.a4lg.com>

This patch is postponed because I will merge this into a larger patchset
with general core disassembler improvements.

Thanks,
Tsukasa

On 2022/07/13 12:51, Tsukasa OI wrote:
> Because XLEN for the disassembler is computed and stored in the `xlen'
> variable, this commit replaces uses of `info->mach' with `xlen'
> (testing for ADDIW / C.ADDIW address sequence).
> 
> opcodes/ChangeLog:
> 
> 	* riscv-dis.c (print_insn_args): Use `xlen' to determine whether
> 	XLEN is larger than 32.
> ---
>  opcodes/riscv-dis.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/opcodes/riscv-dis.c b/opcodes/riscv-dis.c
> index 164fd209dbd..3f69756606e 100644
> --- a/opcodes/riscv-dis.c
> +++ b/opcodes/riscv-dis.c
> @@ -235,7 +235,7 @@ print_insn_args (const char *oparg, insn_t l, bfd_vma pc, disassemble_info *info
>  	    case 'j':
>  	      if (((l & MASK_C_ADDI) == MATCH_C_ADDI) && rd != 0)
>  		maybe_print_address (pd, rd, EXTRACT_CITYPE_IMM (l), 0);
> -	      if (info->mach == bfd_mach_riscv64
> +	      if (xlen > 32
>  		  && ((l & MASK_C_ADDIW) == MATCH_C_ADDIW) && rd != 0)
>  		maybe_print_address (pd, rd, EXTRACT_CITYPE_IMM (l), 1);
>  	      print (info->stream, dis_style_immediate, "%d",
> @@ -433,7 +433,7 @@ print_insn_args (const char *oparg, insn_t l, bfd_vma pc, disassemble_info *info
>  	  if (((l & MASK_ADDI) == MATCH_ADDI && rs1 != 0)
>  	      || (l & MASK_JALR) == MATCH_JALR)
>  	    maybe_print_address (pd, rs1, EXTRACT_ITYPE_IMM (l), 0);
> -	  if (info->mach == bfd_mach_riscv64
> +	  if (xlen > 32
>  	      && ((l & MASK_ADDIW) == MATCH_ADDIW) && rs1 != 0)
>  	    maybe_print_address (pd, rs1, EXTRACT_ITYPE_IMM (l), 1);
>  	  print (info->stream, dis_style_immediate, "%d",
> 
> base-commit: dd4c046506cd4da46b439a2b4f8b6d933ecbb961

      reply	other threads:[~2022-07-30  4:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  3:51 Tsukasa OI
2022-07-30  4:19 ` Tsukasa OI [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=23f34a05-e0a4-5eb6-fa0b-3555f6ce60e7@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    --cc=kito.cheng@sifive.com \
    --cc=nelson.chu@sifive.com \
    --cc=palmer@dabbelt.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).