Skip to content

Conversation

alec-deason
Copy link
Contributor

When passing u64, u32, u16 or u8 values between rust and python the runtime incorrectly handles them as the equivalent signed type which leads to overflows for extreme values. This change adds explicit handling for unsigned types.

I believe this wasn't being caught by the existing tests because the overflow was symmetric in each direction so values would overflow when passed from rust->python and then overflow again when passed in the opposite direction, returning to the initial value. Since the only check being done was that the value returned from the round trip unchanged the tests did not see this happening. This change adds a check in the python guest code which asserts that values which are expected to be unsigned are actually non-negative.

fixes #125

Copy link
Collaborator

@dicej dicej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@dicej dicej merged commit fc16d0c into bytecodealliance:main Nov 18, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OverflowErrors when using u64s

2 participants