| Re: [hatari-devel] The external disassembler is now really external |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] The external disassembler is now really external
- From: Christian Zietz <czietz@xxxxxxx>
- Date: Wed, 24 Aug 2022 20:25:28 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1661365528; bh=TNqcrj73wRlFe8cAdYczEg5o6SO4pHJ+bN0i7ZrZCQ4=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=cD+YPJOZU9MRmUUPweOogw+t3ueROYX7DK1OHXT5ayBJVZ+3MN212l5OtLwDg9Xz3 ASYFKpmo3ZU/0KHhNQTl5fVNRNak2VcQ03hnCbA19kBLYLOAeMti4AIbcMMXjkkd/Q dgJF/BmParlyR28CeCVVCANermQXB/htNtxbhtZ4=
Thomas Huth schrieb:
- Most importantly: 68030 MMU opcodes are incorrectly disassembled as
*FPU* instructions.
Uh, that's bad :-( Could you maybe a bug ticket at
https://github.com/capstone-engine/capstone/issues ?
(otherwise, let me know, then I'll do it)
I would appreciate if you did it. Because there might be questions like
"how is Hatari integrating Capstone", which I could not answer.
PS: Capstone comes with a nice command line tool for disassembly, so it's
even possible to verify this on the command line:
$ cstool m68k40 0xf0394c0000e4995a
0 f0 39 4c 00 fmove.x invalid, fp0
... that should be a pmove instead.
I'm not sure this is the best way of demonstrating the bug to the
Capstone developers. The 68040 does not have PMOVE. It has some other
PMMU instructions, but these differ from the 68030.
Regards
Christian
--
Christian Zietz - CHZ-Soft - czietz@xxxxxxx
WWW: https://www.chzsoft.de/
PGP/GnuPG-Key-ID: 0x52CB97F66DA025CA / 0x6DA025CA