On Thu, Jul 21, 2022 at 7:27 AM Nick Desaulniers <ndesaulniers@xxxxxxxxxx> wrote: > > On Wed, Jul 20, 2022 at 4:23 PM Justin Stitt <justinstitt@xxxxxxxxxx> wrote: > > > > There's been an ongoing mission to re-enable the -Wformat warning for > > Clang. A previous attempt at enabling the warning showed that there were > > many instances of this warning throughout the codebase. The sheer amount > > of these warnings really polluted builds and thus -Wno-format was added > > to _temporarily_ toggle them off. > > > > After many patches the warning has largely been eradicated for x86, > > x86_64, arm, and arm64 on a variety of configs. The time to enable the > > warning has never been better as it seems for the first time we are > > ahead of them and can now solve them as they appear rather than tackling > > from a backlog. > > > > As to the root cause of this large backlog of warnings, Clang seems to > > pickup on some more nuanced cases of format warnings caused by implicit > > integer conversion as well as default argument promotions from > > printf-like functions. > > > > > > Link: https://github.com/ClangBuiltLinux/linux/issues/378 > > Suggested-by: Nick Desaulniers <ndesaulniers@xxxxxxxxxx> > > Signed-off-by: Justin Stitt <justinstitt@xxxxxxxxxx> > > --- > > Previous attempt: (https://patchwork.kernel.org/project/linux-kbuild/patch/20190201210853.244043-1-jflat@xxxxxxxxxxxx/) > > > > Note: > > For this patch to land on its feet, the plethora of supporting patches that > > fixed various -Wformat warnings need to be picked up. Thanfully, a lot > > of them have! > > > > Here are the patches still waiting to be picked up: > > * https://lore.kernel.org/all/20220718230626.1029318-1-justinstitt@xxxxxxxxxx/ > > * https://lore.kernel.org/all/20220711222919.2043613-1-justinstitt@xxxxxxxxxx/ > > Hi Masahiro, Nathan, and Tom, > What are your thoughts for _when_ in the release cycle this should be > picked up? I worry that if we don't remove this soon, we will > backslide, and more -Wformat issues will crop up making removing this > in the future like digging in sand. Justin has chased down many > instances of this warning, and I'm happy to help clean up fallout from > landing this. Otherwise, we probably want to look at picking up Youngmin's patch ASAP. https://lore.kernel.org/all/20220716084532.2324050-1-youngmin.nam@xxxxxxxxxxx/ (This thread, for context for Youngmin: https://lore.kernel.org/llvm/20220720232332.2720091-1-justinstitt@xxxxxxxxxx/) > > > > > scripts/Makefile.extrawarn | 1 - > > 1 file changed, 1 deletion(-) > > > > diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn > > index f5f0d6f09053..9bbaf7112a9b 100644 > > --- a/scripts/Makefile.extrawarn > > +++ b/scripts/Makefile.extrawarn > > @@ -47,7 +47,6 @@ else > > > > ifdef CONFIG_CC_IS_CLANG > > KBUILD_CFLAGS += -Wno-initializer-overrides > > -KBUILD_CFLAGS += -Wno-format > > KBUILD_CFLAGS += -Wno-sign-compare > > KBUILD_CFLAGS += -Wno-format-zero-length > > KBUILD_CFLAGS += $(call cc-disable-warning, pointer-to-enum-cast) > > -- > > 2.37.0.170.g444d1eabd0-goog > > > > > -- > Thanks, > ~Nick Desaulniers -- Thanks, ~Nick Desaulniers
