Hidden field access and debugging features #108
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.
The main part of this PR is fixing a bug when accessing the hidden field. Previously, when loading the payload size from the hidden field before the object, it didn't mask out the
HAS_MOVED_GIVTBL
flag, resulting in wrong object sizes. This PR fixes that. In bothmmtk-ruby
andruby
repos, we encapsulate the access to the hidden field in dedicated functions and make sure the bit masks are applied.In the
ruby
repo, we also disable the code paths that result in re-embedding "heap" arrays and strings, because that is a source of dangling pointer bugs.In the
mmtk-ruby
repo, we introduced theextra_assert!
macro which can be enabled by the "extra_assert" Cargo feature even in release builds. We also introduced a feature for stressing Immix collectors and a saferis_mmtk_object_safe
function.