Dan Sugalski wrote:
At 8:14 PM +0100 1/24/03, Leopold Toetsch wrote:
Of course, you should know, how to prepare arguments for function
Heh, I'm not worried--it certainly won't be the first assembly language I've learned. :)
I knew that.
Just a matter of getting the time to do it, which is the bigger problem.
And guessed this too :-)
... Pity the automagic .s parsing code in JITv1 didn't ultimately work out...Trial to (ab?)use gcc for generating JIT code, probably.
But:
mops.pasm:
JIT/i386 ~800 MOps at 800 MHz Athlon i.e. 1 op/cycle
gcc -O3 (native code) ~300 Mops
Of course this doesn't give real time program values, but shows some optimization potential for tight loops where loop variables can be reduced to bo native integers.
And of course JIT code is not "J" like just, one code segment get's JITed and no there is no run loop, all instructions need the space they occupy, which is currently (size in bytes, with PBC size in ops):
jit.c:838
/* estimate size needed
* 10 times pbc code size seems to be enough for i386
*/
... but computers tend to have more RAM, and the more the fast.
leo
