diff options
author | 2023-08-11 16:03:23 +0200 | |
---|---|---|
committer | 2023-08-20 14:16:59 +0900 | |
commit | 6d4ab2e97dcfbcd748ae71761a9d8e5e41cc732c (patch) | |
tree | 1a392489939efaada411344d41f304bbc8304265 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | kbuild: avoid duplicate warning options (diff) | |
download | wireguard-linux-6d4ab2e97dcfbcd748ae71761a9d8e5e41cc732c.tar.xz wireguard-linux-6d4ab2e97dcfbcd748ae71761a9d8e5e41cc732c.zip |
extrawarn: enable format and stringop overflow warnings in W=1
The stringop and format warnings got disabled globally when they were
newly introduced in commit bd664f6b3e376 ("disable new gcc-7.1.1 warnings
for now"), 217c3e0196758 ("disable stringop truncation warnings for now")
and 5a76021c2eff7 ("gcc-10: disable 'stringop-overflow' warning for now").
In all cases, the sentiment at the time was that the warnings are
useful, and we actually addressed a number of real bugs based on
them, but we never managed to eliminate them all because even the
build bots using W=1 builds only see the -Wstringop-truncation
warnings that are enabled at that level.
Move these into the W=1 section to give them a larger build coverage
and actually eliminate them over time.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions