[clang] [Clang] Consider preferred_type in bitfield warnings (#116760) (PR #116785)

[via cfe-commits]

cor3ntin wrote:

> This does mean that if the preferred and explicit types have different storage requirements we may not warn in all possible cases, but that's a scenario for which the warnings are much more complex and confusing

If I understand the patch correctly, we always warn, but about the wrong thing.

Should we pick the minimum of both sizes? Should we make it an error for a bit-field to be *larger* than the prefered type?



https://github.com/llvm/llvm-project/pull/116785