public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Claudiu Zissulescu <claziss@gmail.com>
Cc: binutils@sourceware.org, fbedard@synopsys.com
Subject: Re: [committed 2/2] opcodes/arc: Implement style support in the disassembler
Date: Wed, 20 Jul 2022 12:50:39 +0930	[thread overview]
Message-ID: <Ytd0h4UXSihhjR50@squeak.grove.modra.org> (raw)
In-Reply-To: <20220718112501.3284580-2-claziss@gmail.com>

On Mon, Jul 18, 2022 at 02:25:01PM +0300, Claudiu Zissulescu via Binutils wrote:
> Update the ARC disassembler to supply style information to the
> disassembler output. The output formatting remains unchanged.

I see lots of fails in the arc gas teststuite.  Please do run the
testsuite.

regexp "^0x[0-9a-f]+ 21c1 006b                  adc.lt  r1,r1,0x1$"
line   "0x000000c4 21c1 006b            adc.lt  r1,r1,1"

It's this one:
> -		(*info->fprintf_func) (info->stream, "%#x", value);
> +		(*info->fprintf_styled_func) (info->stream, dis_style_immediate,
> +					      "%" PRIx32, value);

PRIx32 is wrong anyway, when "value" is an int.  Fixed.

diff --git a/opcodes/arc-dis.c b/opcodes/arc-dis.c
index dbaa96178a8..3490bad4f66 100644
--- a/opcodes/arc-dis.c
+++ b/opcodes/arc-dis.c
@@ -1408,7 +1408,7 @@ print_insn_arc (bfd_vma memaddr,
 					      "%s", rname);
 	      else
 		(*info->fprintf_styled_func) (info->stream, dis_style_immediate,
-					      "%" PRIx32, value);
+					      "%#x", value);
 	    }
 	}
 

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2022-07-20  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 11:25 [committed 1/2] arc: Update missing cipher Claudiu Zissulescu
2022-07-18 11:25 ` [committed 2/2] opcodes/arc: Implement style support in the disassembler Claudiu Zissulescu
2022-07-20  3:20   ` Alan Modra [this message]
2022-07-20 13:51     ` Claudiu Zissulescu Ianculescu

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=Ytd0h4UXSihhjR50@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=claziss@gmail.com \
    --cc=fbedard@synopsys.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).