| Re: [hatari-devel] 68010 [OFF-TOPIC] |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] 68010 [OFF-TOPIC]
- From: Christian Zietz <czietz@xxxxxxx>
- Date: Wed, 9 Dec 2020 14:13:16 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1607519598; bh=EtrUFKldUEgQkTigi1KUqEfnT5FIYajn+kaLB+7dXNY=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=fsRpgMydqHbFOTVGdnuKHjF1inDzSltjC/wF9/V1UvhkuuRgSApuQI6RIfmysPfta oMJ0WThSdQ+k1qcVq4nwsUEAJRnNkIQ8h1JcfyAB7uSzNRDYJuiknW7mXOHUNMqTED +zB7OaTUv8fNgQcuWxffhijV18adq2oJgOd2oOR8=
Thorsten Otto schrieb:
Thats a bit strange, because the _longframe system variable is correctly
set by emutos, but understandable, since there was no machine with 68010
where you could have tested PD at that time.
Pure Debugger does not use the 'longframe' variable or the _CPU cookie.
It has it's own CPU detection routines. In particular, anything that
does not yield the expected result for...
MOVE.B (xxx,PC,D0.W*2),D0
.... (which is a 68020-and-above addressing mode) is treated like a
68000, including the 68010.
Like I said (and Vincent also emphasized), this is *neither* a Hatari
bug *nor* an EmuTOS bug.
Regards
Christian
--
Christian Zietz - CHZ-Soft - czietz@xxxxxxx
WWW: https://www.chzsoft.de/
PGP/GnuPG-Key-ID: 0x52CB97F66DA025CA / 0x6DA025CA