[B2-devel] JIT Compiler: success! ;-)

[<gb...@di...>]

Hi,

> the optlev thing I don't know what it is used for...)

Optimization Level but as I don't and probably won't use the optimizer,
I don't need it.

The JIT still requires have_get_mem_word disabled. It currently achieves
only +30% more speed according to Speedometer. Some drawbacks:

- The JIT-enabled BasiliskII does not look as responsive as before

- 68040 support is broken. Have you ever seen a green scrollbar at
startup ? ;-)

- In 68040 mode, the translation cache tends to be flushed up to three
times more than in 68020/68030 mode. 320 flushes per second opposed to
125 flushes per second. Probably not that costly after all...

- Memory accesses are slow (read: the generated code for it is big) but
this will change when I integrate Direct Addressing.

I have also been experimenting apart what I will name "pessimistic dead
flag calculation elimination". This could provide a one-pass compilation
process since live analysis of flags won't be needed anymore.

My todo list:
- fix 68040 support
- fix support for have_get_mem_word_unswapped
- integrate direct addressing
- integrate, as an option, pessimistic dead flag calculation elimination
- integrate MAE-style cpufunctbl patches
- enable flag calculation through the old pushfl/pop method because the
current one (sahf/seto) is slower on my AMD K6-2. It is activated
through the SAHF_SETO_PROFITABLE flag.
- merge m68k_execute() and m68k_compile_execute() [m68k_go()
replacements] into one function that takes a boolean telling whether or
not the JIT compiler can do its job.

Bye.
-- 
Gwenolé Beauchesne