Fix size of type_id in Object.set_crystal_type_id
#13338
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 type of
crystal_type_id
isInt32
, notLibC::SizeT
. On 64-bit systems this wrong size would write a 64-bit integer into a space that's only suppose to be 32-bit wide.This bug has limited practical effect. Due to byte ordering the memory representation of 32-bit and small 64-bit values are (usually) identical. The type id is never wider than 32-bits so this works correctly. The only negative side effect would be overriding the first 4 bytes of the object data that follows the type id.
This method is only called from
WeakRef.allocate
on an empty object where this is irrelevant.It's sill a bug and needs to be fixed. For the fix I opted to infer the type based on the type of
crystal_instance_type_id
(which is a compiler primitive). The size does not need to be hard-coded into stdlib.