1
0
mirror of https://github.com/TomHarte/CLK.git synced 2024-06-27 01:29:31 +00:00

After rerunning all tests, adds some notes on questionable results.

Also renames a file. But no code changes are currently suggested, at least until I can learn more about DIVU/DIVS.
This commit is contained in:
Thomas Harte 2020-01-04 16:31:45 -05:00
parent 627d3c28ea
commit 937cba8978
2 changed files with 9 additions and 0 deletions

View File

@ -29,3 +29,12 @@ I follow every generated opcode with three words of mostly-random data; this dat
Similarly, all initial register contents are random except that the lowest bit is never set, just in case any of them is used to calculate an address for a word or longword.
So the output is very scattergun approach, with a lot of redundancy.
## Questionable Results
I am presently unconvinced by the results for:
* the N flag on many of the [A/S/N]BCD results, as these often seem to conflict with Bart Trzynadlowski's 68knotes.txt; and
* the alleged results of A7-relative JSR, for which the emulator I was testing against appears to have computed a target address for the value of A7 after pushing the existing PC to the stack, which is unlikely because the first of that instruction's program fetches occurs before any stack activity.
This emulator seems not yet to generate values for the undocumented flags of DIVU and DIVS that match those listed here, but that's through lack of documentation. The objective here is to test my implementation of behaviour I am able to find descriptions of against other people's implementations of that same behaviour, to flush out errors in my comprehension and implementation.