Berry stores compiled bytecode into IRAM, freeing space in heap #14307
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.
Description:
Enabled by default with
#define USE_BERRY_IRAM
, when no PSRAM is present, compiled Berry bytecode is moved into IRAM rather than DRAM. This allows us to use the ~40KB of untapped IRAM (IRAM needs reads/writes to be 32 bits aligned which does not make it suitable for any use).No impact on speed.
Note: only
ktab
(list of constants),blineinfo
(line numbers for debug) andcode
(actual bytecode) are move to IRAM, which makes typically 30%-40% of memory used by custom code.Note2: when using
#define USE_BERRY_DEBUG
, the line number information has its size slightly increased, but can be moved to IRAM, so that's a positive net benefit.Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass