-
Notifications
You must be signed in to change notification settings - Fork 700
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
[wasm2c] Strange issue with double parsing in msvc #2422
Comments
isn't this #2389 ? |
INT_MIN/etc are notorious for being a pain as a numeric constant, the usual workaround is to write it as an expression (-2147483647 - 1). (something about it being technically UB?) |
Ah yes, I think #2389 will fix this. My fix was to append |
|
Closing as duplicate of #2388 |
sbc100
added a commit
that referenced
this issue
May 14, 2024
See WebAssembly/memory64#51 Includes workaround for #2422
sbc100
added a commit
that referenced
this issue
May 15, 2024
See WebAssembly/memory64#51 Includes workaround for #2422
sbc100
added a commit
that referenced
this issue
May 15, 2024
See WebAssembly/memory64#51 Includes workaround for #2422
sbc100
added a commit
that referenced
this issue
May 15, 2024
See WebAssembly/memory64#51 Includes workaround for #2422
sbc100
added a commit
that referenced
this issue
May 15, 2024
See WebAssembly/memory64#51 Includes workaround for #2422
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some reason INT_MIN is not parsing correctly under MSVC..
Under MSVC this produces:
i.e. only adding
.0
at the end causes the sign bit to be preserved.Gcc and clang both (correctly I believe) produce:
The text was updated successfully, but these errors were encountered: