-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Add -Wms-bitfield-padding warning when possible #139828
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
base: main
Are you sure you want to change the base?
Conversation
This is a draft PR as it might produce a bunch of noise, I've got a PR to fix the cases I can repeat locally: #139825 I suspect issues may occur in other configs and I'd like to hear from others before making this a non-draft PR |
I applied changes from both PRs, and I'm seeing the following warnings (heavily deduplicated):
Most of them are in headers, so you should take care of them before people's build logs are flooded. P.S. I'm not really doing 2-stage builds. What I do is that I use nightly builds from https://apt.llvm.org, and update 1-2 times per month on average. TIL that the second stage of 2-stage builds is not compatible with |
Thank you very much! I'll try to add the fixes for those ones. What targets do you have enabled? |
Only X86 |
would you mind checking now that #139825 has been merged? |
I'll do a 2-stage build again, now with all the targets enabled. Should I enable any additional diagnostic flags for the second stage? |
maybe I think I got everything, but I was dealing with some slightly irksome lbc++ linker problems |
In addition to all targets, I also built clang-tools-extra, and there's a warning there:
|
ah ha, thank you! |
I figured out I should compile lld and lldb, too. Here are additional warnings:
|
ah ha, lets see if I can convince my local build to just build all the things |
No description provided.