Add experimental support for mapping bytecode to an external data area #1409
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add config option DUK_USE_EXTBC_CHECK. * Update low memory example with DUK_USE_EXTBC_CHECK (commented out).
Initial experimental external bytecode support: * Add a hook into the compiler: when the final function template is being created, create the fixed buffer and then offer the bytecode opcode part to a used provided DUK_USE_EXTBC_CHECK() macro to see if it should be mapped to a user supplied data area. * For now there's no release mechanism: user code can free the mapped data area when it's 100% Duktape cannot be referencing it any longer. Ideally there would be a lifecycle notification. * Change duk_hbuffer pointer typing to duk_uint8_t: use "duk_uint8_t *" instead of "void *".
svaarala
force-pushed
the
external-bytecode-buffer-initial
branch
from
dd2a84b
to
b9fbcad
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
DUK_USE_EXTBC_CHECK()which allows an application to map the bytecode of a function to an external data area. This allows Ecmascript function bytecode to be e.g. copied to memory-mapped flash which reduces actual RAM usage; usefulness depends on the target architecture.This is a very early experimental version: DUK_USE_EXTBC_CHECK() is called and if it returns a non-NULL pointer the bytecode is used from the pointer provided. There's no GC integration: the application must ensure that the external pointer remains valid for the lifetime of the Ecmascript function (without having any hook to know that).
Tasks: