JIT + phxass compilation

[ziosante]

Hi, i discovered a problem with JIT 68k emulation.
I tried to compile with PhxAss an old assembler source I written for Amiga 68k.
For some strange reason if I enable JIT in WinUAE, PhxAss was unable to compile the source.

If I disable JIT the source compiles without problem.

I remeber I've compiled successfull this sources with Amithlon(that uses JIT like WinUAE).

What can I post here to identify the problem?

Thanks.

[Toni Wilen]

Most likely this has nothing to do with 3.2 betas -> moved here.

I haven't noticed any problems with phxass in JIT mode.

First test it without startup-sequence (and with confirmed non-modified KS ROM) to confirm it is not side-effect caused by some other background program or patch. Then with setpatch.

[ziosante]

Hi,
cold started kickstart 40.68 A1200 plain without startup-sequence so without any patch or resident module.
The problem is the same(I can confirm too with WinUAE 3.1.0).
The problem does not appear with all sources, I successfull compile other small assembler sources but there is a source of about 36000 lines that fails in JIT.
I used Phxass 4.44(tested version 4.39 and 4.40, same problem). I can post here the source if you want to make a test.
Attached my configuration and a screenshot.

[Toni Wilen]

Your config has a bit too many expansions for JIT (or anything else) debugging. Remove everything "useless" like accelerator board, RTG board and so on.

Also test with 68040. (You don't gain anything with 68060, unless you want to emulate missing instruction exceptions but that does not work with JIT anyway)

If it still happens, switch JIT to indirect mode. What about if you enable Hard flush JIT option?

[ziosante]

Hi Toni,
disabling PPC the problem is solved, tested 68040 and 68060 cpu options and both work.
Attached the configuration I've found to work for me.

[PeterK]

Indeed, most likely this has nothing to do with JIT or WinUAE. Compiled all my progs with PhxAss 4.44 or the new 4.46 on WinUAE with JIT enabled. Always in less than 1 second !!

http://eab.abime.net/showpost.php?p=994297&postcount=51

[Toni Wilen]

It probably is Blizzard RAM layout "problem". It can be JIT hostile but disabling JIT direct should fix it (which also makes JIT slower).

[ziosante]

The problem solves if I configure 32 MB of Z3 Fast RAM + 32 MB of expansion card memory(this one seems to be obbligatory for PPC to work).
But when OS 3.9 is loaded I must edit with a program like "Scout" the "expansion memory" region(that should be the Z3 Fast RAM) and give it more priority than RAM relative to accelerated board memory.
In this way I've no problem with Phxass assembling when JIT is enabled and WarpOS seems to wroks well.

I must make some more tests to see what happens when Z3 Fast RAM is low and the system starts using accelerated board memory.

Test: when Z3 Fast RAM go low and the OS starts using accelerated board memory the problem is back again. Seems like 68k JIT and PPC could have some problem sharing accelerated board memory(I don't know if the problem is PhxAss, i tried making some debug with MuForce and MuGuardianAngel but no problem raise lke invalid memory access or anthing else).