Merged
Conversation
zharinov
force-pushed
the
feat/aligned-bytecode-storage
branch
from
9e97d5f to
46ec364
Compare
zharinov
changed the title
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
1 participant
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.
Summary
AlignedVectype usingVec<Block>trick for 64-byte alignmentinclude_query_aligned!macro for zero-copy embedded bytecodeByteStorageenum withStaticandAlignedvariantsfrom_aligned,from_static,from_path,loadModule::from_bytesWhy
Bytecode sections are 64-byte aligned internally. For DFA deserialization and cache efficiency, the buffer itself must start at a 64-byte boundary. Standard
Vec<u8>provides no alignment guarantees.