There are two fundamental problems: 1) uninit warning has false positives. 2) people disagree what is the expected behavior of -Wall.
1) can only be solved by improving the analysis. The new option is a reasonable way to solve 2), unless you think the only way to solve it is to change the behavior of -Wall, or ask concerned user to explicitly use -Wno-error=... or white list the warning options they care. David On Wed, Jul 10, 2013 at 12:36 PM, Gabriel Dos Reis <g...@integrable-solutions.net> wrote: > On Wed, Jul 10, 2013 at 2:27 PM, Xinliang David Li <davi...@google.com> wrote: >> On Wed, Jul 10, 2013 at 12:05 PM, Gabriel Dos Reis >> <g...@integrable-solutions.net> wrote: >>> On Wed, Jul 10, 2013 at 2:01 PM, Xinliang David Li <davi...@google.com> >>> wrote: >>>> What about introducing a new blanket warning kind that excludes >>>> anything with false positives? something like -WALL ? >>> >>> I am doubtful "more ropes" is the answer. >>> >> >> Reason? > > It adds one too-many options to existing minefield without > solving the underlying fundamental problem. > > -- Gaby
