[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] target-m68k: Implement bfffo
From: |
Andreas Schwab |
Subject: |
Re: [Qemu-devel] [PATCH] target-m68k: Implement bfffo |
Date: |
Tue, 15 Nov 2016 22:59:42 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
On Nov 15 2016, Richard Henderson <address@hidden> wrote:
> On 11/15/2016 10:12 PM, Laurent Vivier wrote:
>> Le 15/11/2016 à 22:07, Laurent Vivier a écrit :
>>> Le 15/11/2016 à 21:44, Richard Henderson a écrit :
>>>> @@ -5415,6 +5450,8 @@ void register_m68k_insns (CPUM68KState *env)
>>>> INSN(bfop_reg, eac0, fff8, BITFIELD); /* bfchg */
>>>> INSN(bfop_mem, ecc0, ffc0, BITFIELD); /* bfclr */
>>>> INSN(bfop_reg, ecc0, fff8, BITFIELD); /* bfclr */
>>>> + INSN(bfop_mem, edc0, ffc0, BITFIELD); /* bfffo */
>>>> + INSN(bfop_reg, edc0, fff8, BITFIELD); /* bfffo */
>>>
>>> In my doc, bfffo is 0xE9C0.
>>
>> I think my doc [1] is wrong, because it is the same as bextu and the
>> as/objdump gives me 0xEDC0.
>
> My doc gives the same wrong opcode on the bfffo description page. It
> confused me for some time until I scrolled to the opcode map at the end of
> the document, where it is correctly identified as EDC0.
The printed manual has the correct opcode, it is only wrong in the PDF.
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."