I often read on the mailing list people saying "who cares about W=2 builds anyway?". At least I do. Not that I want to fix all of them, but on some occasions, such as new driver submissions, I have often found a couple valid diagnostics in the W=2 output.
That said, the annoying thing is that W=2 is heavily polluted by one warning: -Wtype-limits. Try a gcc W=2 build on any file and see the results for yourself. I suspect this to be the reason why so few people are using W=2. This series removes gcc's -Wtype-limits in an attempt to make W=2 more useful. Those who do not use W=2 can continue to not use it if they want. Those who, like me, use it for time to time will get an improved experience from the reduced spam. Patch #1 deactivates -Wtype-limits. Extra details on statistics, past attempts and alternatives are given in the description. Patch #2 clean-ups the local kbuild -Wno-type-limits exceptions, patches #3 and #4 undo some of the local workarounds which silenced that warning by uglifying the code. Signed-off-by: Vincent Mailhol <[email protected]> --- Changes in v2: - Add two more patches to clean up some -Wtype-limits workarounds - Collect the Reviewed-by tags. Link to v1: https://lore.kernel.org/r/[email protected] --- Vincent Mailhol (4): kbuild: remove gcc's -Wtype-limits kbuild: cleanup local -Wno-type-limits exceptions overflow: Remove is_non_negative() and is_negative() minmax: remove useless cast in __is_nonneg() drivers/gpu/drm/Makefile | 1 - fs/btrfs/Makefile | 1 - include/linux/minmax.h | 5 +---- include/linux/overflow.h | 10 ++-------- scripts/Makefile.warn | 4 +++- 5 files changed, 6 insertions(+), 15 deletions(-) --- base-commit: 3e7f562e20ee87a25e104ef4fce557d39d62fa85 change-id: 20251205-remove_wtype-limits-c77eb46d09c2 Best regards, -- Vincent Mailhol <[email protected]>
