From their web page:
http://luajit.org/status.html
Quote:
The JIT compiler only generates code for CPUs with support for SSE2 instructions. I.e. you need at least a P4, Core 2/i5/i7 or K8/K10 to get the full benefit.
...
Obviously there will be many bugs in a VM which has been rewritten from the ground up. Please report your findings together with the circumstances needed to reproduce the bug. If possible reduce the problem down to a simple test cases.
...
The JIT compiler is not complete (yet) and falls back to the interpreter in some cases.
...
Many known issues cause a NYI (not yet implemented) trace abort message. E.g. for calls to vararg functions or many string library functions.
Look, fine if it works for you. Great if it works faster than the normal Lua, and doesn't crash. If you want to try it, and report back that it not only doesn't cause any problems, but runs much faster than normal, that would be good to know.
Mind you, I virtually never look at MUSHclient and think that it is doing something too slowly. Even with Fiendish's mapper cranked up in size to take up a large swag of screen space, and a big search depth, it seems to be fast and responsive. Maybe his example of a very fast speedwalk would be a bit quicker (mind you, in that particular case the "slow" version was only 9 seconds slower, to cross a couple of continents, than the faster version).
But there is nothing stopping you dropping in the DLL and trying it, is there? |