Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix a few unsigned/signed readI/ULEB mismatches #232

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

marler8997
Copy link
Contributor

There was a few mismatches where readULEB was being called with signed types. I fixed those and collapsed the readILEB/readULEB into one readLEB function that just uses the signedness of the native type to determine which underlying function to use.

There was a few mismatches where readULEB was being called with signed
types. I fixed those and collapsed the readILEB/readULEB into one
readLEB function that just uses the signedness of the native type to
determine which underlying function to use.
@malcolmstill
Copy link
Owner

Thanks @marler8997!

Was this just something you noticed in the code, or was this causing some issue during parsing (and if so under what circumstances)?

@malcolmstill malcolmstill merged commit ed1860f into malcolmstill:master Oct 18, 2024
16 checks passed
@marler8997
Copy link
Contributor Author

It was just something I noticed. I was referencing your code for one of my projects and ended up having a mismatch that actually did result in an issue. I think the only mismatches you actually had here were for valtype and reftype which only use up to 8 bits.

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.

2 participants