Original Post
🔒 Locked
Context.Prepare
Advertisement
It is necessary to call Prepare() to reset the context before starting the execution again.
I could make Prepare() a little smarter by verifying if it is the same function ID that is being passed, and if so use the information that is already known. That would save a little overhead, where bytecode address is fetched, and stack space is verified, etc.
I could make Prepare() a little smarter by verifying if it is the same function ID that is being passed, and if so use the information that is already known. That would save a little overhead, where bytecode address is fetched, and stack space is verified, etc.
Hi
As WitchLord said, probably is needed to call prepare() each time ,i dont have confirmed this, but i use a modified version where i call prepare at the script compilation, and call execute() each frame, without calling prepare, avoiding the overhead
The scripts use the last stack state for each new frame, with script/context pairs
I dont know what is the current implementation state of the ASM VM, but a few changes are needed, like updating the eip at the execution ret
Lioric
As WitchLord said, probably is needed to call prepare() each time ,i dont have confirmed this, but i use a modified version where i call prepare at the script compilation, and call execute() each frame, without calling prepare, avoiding the overhead
The scripts use the last stack state for each new frame, with script/context pairs
I dont know what is the current implementation state of the ASM VM, but a few changes are needed, like updating the eip at the execution ret
Lioric
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement