-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Remove dead code from sys::windows::c #31782
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
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
⌛ Testing commit 0a6f35b with merge a2ee00f... |
💔 Test failed - auto-win-gnu-32-nopt-t |
I can't really get cross-compiling set up, but I think this fixes it for 32-bit. |
If this bounces I've got a simple script to just mock compile the repo, which may be useful for ensuring that other platforms just compile |
Thanks! I have no idea what that script does... |
Ah if you tweak the first two lines to uncomment the right stage/triple and just run it inside of a checkout of the compiler it will "bootstrap" that target into a directory called |
⌛ Testing commit 94db864 with merge b8e2d98... |
💔 Test failed - auto-win-gnu-32-nopt-t |
mingw really does not like me... I have reinstalled msys and 64- and 32-bit mingw and made a fresh checkout and rebuild of rust. But cross-compiling seems out of reach for me. And I tried your script. This pr should work now, but untested for 32-bit. |
I tested this out locally and got (for the MSVC targets)
Both the MinGW targets compiled with no warnings, however. |
Thanks so much for testing this! A little cleanup is not worth all the effort this takes... I don't understand why |
@pitdicker Which is why the message says |
@retep998 The problem is the later stages deny warnings. So I am not sure if compiling fails with this warning, and if so, why? |
@pitdicker oh good point! If that ends up being the only error then this is indeed probably good to go, I only compiled in stage0 |
They say in Dutch when you don't succeed the first two times: third time is shipping rights :). Let's hope |
⌛ Testing commit 98fa5ac with merge 321a60b... |
I am not entirely sure I have got everything right, but if it compiles it is ok probably... I tested it with msvc x86_64 and gnu. Somehow a lot of `EXCEPTION-*` constants are dead code when running test, no idea why. I have put `#![cfg_attr(test, allow(dead_code))]` at the top for this.
I am not entirely sure I have got everything right, but if it compiles it is ok probably...
I tested it with msvc x86_64 and gnu.
Somehow a lot of
EXCEPTION-*
constants are dead code when running test, no idea why.I have put
#![cfg_attr(test, allow(dead_code))]
at the top for this.