|Re: [hatari-devel] New blitter code for xcount=1 nfsr=1|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Le 16/09/2020 à 23:31, Thomas Huth a écrit :
Am Wed, 16 Sep 2020 17:30:50 +0200
schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:
Le 11/09/2020 à 09:23, Nicolas Pomarède a écrit :
Any chance you could add that test from BLIT.ZIP to the "make test"
regression test suite?
that's planned to be next on my todo list :) It's indeed a good
test suite because it really checks many combinations and it should
be rather simple to add to the test suite.
I made a "blitter" test to be run in the tests directory (see
But I get an error when "run_test.sh" is using "--tos none" ; with
debugging I see hatari reaches an illegal instruction then exits
If I use "--tos emutos", then the blitter is working and succeeds as
Any idea why --tos none is causing an error ?
Yes - if you run with --trace cpu_disasm, you can see this before it
jumps to the fake TOS ROM to print the panic message:
cpu video_cyc=4760 188@9 : 0000146E 3f3c 0026 MOVE.W #$0026,-(A7)
cpu video_cyc=4772 200@9 : 00001472 4e4e TRAP #$0e
That means something tried to execute Supexec() which is not
implemented in the fake ROM. The fake TOS is indeed very, very limited.
So instead of using the PCSTART.O startup code in the .prj file, you
have to use startup.s from the tests directory there instead, to make
sure that there are no unwanted OS calls done by the startup code.
Alternatively, we could also try to implement Supexec() and then
run this test with "--bios-intercept on" ... but there might be more
missing OS calls later, so I'm not sure whether that's worth the
does it mean that for now only C program compiled with AHCC and this
startup.s code will work with --tos none ? It won't work either if the C
program is compiled with gcc ?
I don't know if we should add more OS calls to the fake TOS, but maybe
we could add emutos as a required dependancy to run the tests ?
But in that case we must be sure that the emutos version used does not
have unwanted side effect when a new emutos version is released that
could make a test fails while it worked with previous emutos version.
That the advantage of the fake TOS, we know it's "stable" (but it lacks
some OS calls).
I don't have ahcc installed on my setup ; could you compile blitemu.c
and send it to me and then I will push the blitter test to the git repo ?