On 5/27/19 10:39 AM, Yoshinori Sato wrote:
> On Fri, 24 May 2019 00:07:57 +0900,
> Richard Henderson wrote:
>> Obviously there are still a few inconsistencies in the
>> format strings used for the immediates, but the format
>> is readable and it is easy to look at the opcode to see
>> how our decod
On Tue, 28 May 2019 02:47:40 +0900,
Aleksandar Markovic wrote:
>
> On May 27, 2019 5:44 PM, "Yoshinori Sato"
> wrote:
> >
> > On Fri, 24 May 2019 00:07:57 +0900,
> > Richard Henderson wrote:
> > >
> > > Here's a sample of the new output, taken from u-boot.bin:
> > >
> > > IN:
> > > 0xfff8000a: f
On May 27, 2019 5:44 PM, "Yoshinori Sato"
wrote:
>
> On Fri, 24 May 2019 00:07:57 +0900,
> Richard Henderson wrote:
> >
> > Here's a sample of the new output, taken from u-boot.bin:
> >
> > IN:
> > 0xfff8000a: fb 12 00 01 00 00 mov.l #0x0100, r1
> > 0xfff80010: fb 32 f0 13 00 00
On Fri, 24 May 2019 00:07:57 +0900,
Richard Henderson wrote:
>
> Here's a sample of the new output, taken from u-boot.bin:
>
> IN:
> 0xfff8000a: fb 12 00 01 00 00 mov.l #0x0100, r1
> 0xfff80010: fb 32 f0 13 00 00 mov.l #0x13f0, r3
> 0xfff80016: 43 13
Here's a sample of the new output, taken from u-boot.bin:
IN:
0xfff8000a: fb 12 00 01 00 00 mov.l #0x0100, r1
0xfff80010: fb 32 f0 13 00 00 mov.l #0x13f0, r3
0xfff80016: 43 13 sub r1, r3
0xfff80018: fb 22 00 ea f9 ff mov.l #-398
