-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update/fix CheckSizeType cmake check #18309
Conversation
@thewtex, I think you originally contributed the forked version of CheckTypeSize... a very long time ago now. The main concern I have is not knowing which version of cmake we should fork CheckTypeSize from. I chose v3.10.2 mostly arbitrarily and seems to work nicely.. at least of me locally. |
I think #18084 should be excluded from the Fixes list, as we don't want it to auto-close and the issue has more to do with Node.js upgrade. |
Although it looks like Github only marks the first issue in the list as auto-close anyway... |
Done. |
Good to land? |
Update the CheckTypeSize files to v3.10.2 (mostly arbitrary version, but this is what we use in CI). Local patch to CheckTypeSize is not much smaller. Instead of executing the program and using the return value (doesn't work for return values greater than 255), we simply inject `-oformat=wasm` onto the link command, and then we can use `strings` on the binary just like the upstream check. This is basically a single line patch against upstream now. Fixes: #18278 #18238 #17268 #18084 #17811
Update the CheckTypeSize files to v3.10.2 (mostly arbitrary version).
Local patch to CheckTypeSize is not much smaller. Instead of executing the program and using the return value (doesn't work for return values greater than 255), we simply inject
-oformat=wasm
onto the link command, and then we can usestrings
on the binary just like the upstream check. This is basically a single line patch against upstream now.Fixes: #18278 #18238 #17268 #17811