On 05/01/2026 at 13:24, Nicolas Schier wrote: > On Thu, Jan 01, 2026 at 04:21:38PM +0100, Vincent Mailhol wrote: >> 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. >> >> Signed-off-by: Vincent Mailhol <[email protected]> >> --- >> Changes in v4: >> >> - Remove patch #3. >> - Aside from minor changes in the patch descriptions, this is >> basially a revert to v1. >> >> Link to v3: >> https://lore.kernel.org/r/[email protected] > > just to prevent confusions: As Dan silenced the Smatch warning caused > by patch #3 [1] (thanks!), the additional comment patch [2] is obsolete > and v3 of the series is a more complete version than v4.
Exactly! Thanks to Daniel's effort we finally have a complete fix. Let me know if you need any actions from my side. Otherwise, I will assume that my part of the work is done here and will just wait for the v3 to be picked. (I am so happy to start 2026 by getting rid of this annoying -Wtype-limits spam :D) Yours sincerely, Vincent Mailhol
