diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-07-27 13:17:41 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-07-27 13:17:41 -0700 |
| commit | 6e8d666e925333c55378e8d5540a8a9ee0eea9c5 (patch) | |
| tree | 68776cc543e97cda5bd003237fd2aa4cad585602 /scripts/Makefile.ubsan | |
| parent | 468fc7ed5537615efe671d94248446ac24679773 (diff) | |
| download | linux-6e8d666e925333c55378e8d5540a8a9ee0eea9c5.tar.bz2 | |
Disable "maybe-uninitialized" warning globally
Several build configurations had already disabled this warning because
it generates a lot of false positives. But some had not, and it was
still enabled for "allmodconfig" builds, for example.
Looking at the warnings produced, every single one I looked at was a
false positive, and the warnings are frequent enough (and big enough)
that they can easily hide real problems that you don't notice in the
noise generated by -Wmaybe-uninitialized.
The warning is good in theory, but this is a classic case of a warning
that causes more problems than the warning can solve.
If gcc gets better at avoiding false positives, we may be able to
re-enable this warning. But as is, we're better off without it, and I
want to be able to see the *real* warnings.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts/Makefile.ubsan')
| -rw-r--r-- | scripts/Makefile.ubsan | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/scripts/Makefile.ubsan b/scripts/Makefile.ubsan index 77ce538268b5..8ab68679cfb5 100644 --- a/scripts/Makefile.ubsan +++ b/scripts/Makefile.ubsan @@ -14,8 +14,4 @@ ifdef CONFIG_UBSAN ifdef CONFIG_UBSAN_ALIGNMENT CFLAGS_UBSAN += $(call cc-option, -fsanitize=alignment) endif - - # -fsanitize=* options makes GCC less smart than usual and - # increase number of 'maybe-uninitialized false-positives - CFLAGS_UBSAN += $(call cc-option, -Wno-maybe-uninitialized) endif |