Bugfix: Use Base.aligned_sizeof instead of sizeof in Mmap.mmap #58998
+17
−5
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 purpose of this PR is to fix #58982 .
The current (bugged) behaviour is:
This is because
Mmap
erroneously usessizeof
instead ofBase.aligned_sizeof
to compute the number of elements (32 ÷ 9 == 3
).This has gone undetected for a long time because
sizeof(T) == Base.aligned_sizeof(T)
is true for most types including structs. (Padding is to a multiple of 8 bytes is included insizeof(T)
)closes #58982
edit:
Previously,
sizeof
would throw an error exception when presented with a non-mappable type such asRef
.This occurred within the default argument generation.
Base.aligned_sizeof
does not error here, and this is instead caught in the dedicatedisbits
check.This seems desirable and I changed the test to require an
ArgumentError
.