public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Frager, Neal" <neal.frager@amd.com>
To: Alan Modra <amodra@gmail.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH v6 1/2] opcodes: microblaze: Add new bit-field instructions
Date: Thu, 19 Oct 2023 06:40:31 +0000	[thread overview]
Message-ID: <E590BA5E-F393-4D17-AF76-8F553836DB21@amd.com> (raw)
In-Reply-To: <ZTCoMC0x2HiyhH/n@squeak.grove.modra.org>

Hi Alan,


> Le 19 oct. 2023 à 05:53, Alan Modra <amodra@gmail.com> a écrit :
> 
> On Thu, Oct 19, 2023 at 02:10:41PM +1030, Alan Modra wrote:
>>> On Sun, Oct 15, 2023 at 04:48:29PM +0000, Frager, Neal wrote:
>>> In any case, thank you for your review, fixing this issue and committing the patch!
>> 
>> Commit bb0d05ff74fd caused
>> FAIL: objdump -S
>> FAIL: objdump --source-comment
>> on microblaze-linux-gnu.
> 
> Assembling and attempting to disassemble this
> .text
> .long 0x65005f5f
> should give something to look at.  I see
> 
> $ binutils/objdump -d xxx.o
> xxx.o:     file format elf32-microblaze
> 
> 
> Disassembly of section .text:
> 
> 00000000 <.text>:
> Aborted (core dumped)
> 

Thank you for sharing this.  I believe I know the root cause.  These new instructions start with the most significant byte 0x64.  I think the disassembler code is ignoring bit 24 and treating 0x65 as an instruction with bad parameters.

I am confident I can fix it.  I just need to get in front my a PC.

I will send you a patch that fixes this shortly.

Thanks for sharing this!

Best regards,
Neal Frager
AMD

> 
> --
> Alan Modra
> Australia Development Lab, IBM

  reply	other threads:[~2023-10-19  6:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  7:28 Neal Frager
2023-10-13  7:28 ` [PATCH v6 2/2] gas: testsuite: microblaze: Add new bit-field tests Neal Frager
2023-10-17 22:58   ` Michael Eager
2023-10-15 16:30 ` [PATCH v6 1/2] opcodes: microblaze: Add new bit-field instructions Michael Eager
2023-10-15 16:48   ` Frager, Neal
2023-10-19  3:40     ` Alan Modra
2023-10-19  3:53       ` Alan Modra
2023-10-19  6:40         ` Frager, Neal [this message]
2023-10-19 10:23           ` Alan Modra
2023-10-19 13:20         ` Frager, Neal
2023-10-19 21:30           ` Alan Modra
2023-10-20  6:28             ` Frager, Neal

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=E590BA5E-F393-4D17-AF76-8F553836DB21@amd.com \
    --to=neal.frager@amd.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    /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).