Const-propagate some offsets in VMOffsets
#8806
Merged
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.
Before this commit all offsets to all fields in
VMOffsets
were stored as fields withinVMOffset
itself. All of the fields at the start ofVMOffsets
, however, are statically known given the pointer size. Notably this means that the use ofHostPtr
in the runtime still was forcing a dynamic lookup of these static offsets.This commit refactors this to reflect all static offsets based solely on the pointer size in the
PtrSize
trait, removing all the fields fromVMOffsets
. All the dynamically sized fields, however, remain inVMOffsets
.