From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: <gdb@sourceware.org>
Subject: Re: Is this "gdb disassembler" code still needed?
Date: Wed, 31 Jul 2013 16:24:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1307311715470.32382@tp.orcam.me.uk> (raw)
In-Reply-To: <878v1w34ms.fsf@talisman.default>
On Wed, 26 Jun 2013, Richard Sandiford wrote:
> > Other than that I am fairly sure the behaviour is intentional, so except
> > from any microMIPS change to match the MIPS16 variant please refrain from
> > fiddling with these bits until I am done with the change proposed here:
> >
> > http://sourceware.org/ml/binutils/2012-05/msg00183.html
> > http://sourceware.org/ml/binutils/2012-06/msg00114.html
>
> OK, thanks. I'll change microMIPS to match MIPS16 like you say.
What happened to this code after your recent changes? I get rubbish in
disassembly now, e.g.:
Dump of assembler code for function t1:
0x00400991 <+0>: save a0-a3,32,ra,s1
0x00400995 <+4>: addiu s1,sp,16
0x00400997 <+6>: lw v1,0x4009f4 <t1+99>
0x00400999 <+8>: lw v0,0x4009f0 <t1+95>
0x0040099b <+10>: move t9,v1
0x0040099d <+12>: move t8,v0
0x0040099f <+14>: lw v0,24(s1)
0x004009a1 <+16>: move a1,t9
0x004009a3 <+18>: move a0,t8
0x004009a5 <+20>: jal 0x400da0 <exit@mips16plt+15>
0x004009a9 <+24>: nop
[...]
Maciej
next prev parent reply other threads:[~2013-07-31 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 18:35 Richard Sandiford
2013-06-26 19:08 ` Maciej W. Rozycki
2013-06-26 22:10 ` Richard Sandiford
2013-07-31 16:24 ` Maciej W. Rozycki [this message]
2013-07-31 17:24 ` Richard Sandiford
2013-07-31 21:58 ` Maciej W. Rozycki
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=alpine.DEB.1.10.1307311715470.32382@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=rdsandiford@googlemail.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