Introduce the memory_base field in the BM file metadata#486
Open
redoste wants to merge 1 commit into
Open
Conversation
This makes BM bytecode compiled from Bang significantly smaller because the stack is no longer included in the file. Furthermore, debasm looks way cleaner because it doesn't print the stack anymore.
Member
|
@redoste this looks interesting. I'll take a look into it a bit later, sorry. Thank you for the PR! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This makes
bmbytecode compiled frombangsignificantly smaller because the stack is no longer included in the file.Furthermore,
debasmlooks way cleaner because it doesn't print the stack anymore.The behavior of native targets remains the same.