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
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to