| Re: [hatari-devel] WinUAE CPU core disassembler output options |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] WinUAE CPU core disassembler output options
- From: Christian Zietz <czietz@xxxxxxx>
- Date: Sat, 8 Oct 2022 15:51:29 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1665237092; bh=l8EfSN2SL7M8yptSssQxqlBPrbjGWPfyr5TlozQm7co=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=F50YEGaTJClTaj6rnjgZHHX0zM4vXQBGcXYAy+ia+vmmn3qWDioVoTL2mMaw/8bP3 XruclFoFhZ1KImx8HGFYa4HgH2gIjuVnbACrAtBnC0RRkMo+t5zOAq8F+4EdZBTcBe PDkJyoJlKy27RzsM9VnSQ0D+BFEVfgw2J1ZHz9uc=
Eero Tamminen schrieb:
Attached patch adds preliminary support for controlling UAE disassembly
output.
It allows configuring all CPU core disassembly flags except the
DISASM_FLAG_ABSSHORTLONG one for address length of shorts (8 vs 4 hex
chars).
This was inspired by Christian's complaint about its too cluttered
output at atari-forum, and remembering that Toni added already some
output options to CPU core disassembler.
Comments?
I just tested your patch and highly appreciate it. Thank you! It allows
me to configure the UAE disassembly to be much more to my liking. And
yes, I'm aware that everyone has their personal preference; therefore,
it's good that it can be configured from within Hatari now.
One thing I haven't figured out, though: Which bit-flag can be used to
disable the "(T)" or "(F)" annotation following conditional branches? As
it is (understandably) based on the *current* state of the CPU flags, I
find it confusing and would like to suppress it.
Regards
Christian
--
Christian Zietz - CHZ-Soft - czietz@xxxxxxx
WWW: https://www.chzsoft.de/
New GnuPG-Key-ID: 0x8708B34C827B159E