Ok, thanks, I will check this out and see what it could look like.

After some more testing, it appears that using the JIT with appropriate settings just makes performance so good that this is not required anymore! (JIT compiled code is just incredibly faster).

The first time I tried the JIT, I forgot to add the asEP_INCLUDE_JIT_INSTRUCTIONS option, hence the poor performance, By the way, why would this option not be automatically added to the engine when a JIT Compiler is registered?

Are you using the JIT compiler from here

The forum must not like direct links. Are you using the JIT compiler from here . If so could you post some results or a comparison? I haven't tried the JIT compiler. Angelscript has been fast enough for anything I've tried to do.

The forum must not like direct links. Are you using the JIT compiler from here . If so could you post some results or a comparison? I haven't tried the JIT compiler. Angelscript has been fast enough for anything I've tried to do.

ThyReaper,

Those are some pretty good results. I am going to try this out when a I get a chance. Are there any things to watch out for, or is it pretty much plug and play? From the brief docs on Github it seems like its just a matter of registering the JIT compiler with the script engine and then business as usual. Great job, and thanks for the contribution!

Tony

After some more testing, it appears that using the JIT with appropriate settings just makes performance so good that this is not required anymore! (JIT compiled code is just incredibly faster).

The first time I tried the JIT, I forgot to add the asEP_INCLUDE_JIT_INSTRUCTIONS option, hence the poor performance, By the way, why would this option not be automatically added to the engine when a JIT Compiler is registered?

I'll consider adding some check for this, though probably not to automatically turn on asEP_INCLUDE_JIT_INSTRUCTIONS. That wouldn't work with pre-compiled bytecode anyway.

I'll consider adding some check for this, though probably not to automatically turn on asEP_INCLUDE_JIT_INSTRUCTIONS. That wouldn't work with pre-compiled bytecode anyway.

That's right, I had not thought about this!

And yes, that's the JIT I am using, I don't think there is any other anyway... I have just found a small memory leak, but otherwise it is really worth it! Any chance this would become integrated with angelscript directly in the future?

And yes, that's the JIT I am using, I don't think there is any other anyway... I have just found a small memory leak, but otherwise it is really worth it! Any chance this would become integrated with angelscript directly in the future?

No. I have no plans to make this or any other JIT compiler part of the AngelScript SDK. BlindMind's JIT compiler is a completely separate project and is best maintained that way.

I believe BlindMind has made a good job of making the integration of the JIT compiler as smooth as possible anyway.