Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp2114774ybe; Thu, 12 Sep 2019 04:53:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqzS7I/iK+b/IkkKXLGA6lK2DrGKnB1z9JMeW49mvbPIRSAUC38rUzzt1+SvBNa2k6R2ht/Z X-Received: by 2002:a17:906:b2d3:: with SMTP id cf19mr14993662ejb.75.1568289217526; Thu, 12 Sep 2019 04:53:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568289217; cv=none; d=google.com; s=arc-20160816; b=N8zfvnHxRUGF8ig/DBydJiQZqEEC6LPTVOUx0Ks0+XFWNBC/7ErBjiS//HK/Srjsg9 q352xB3acYJtjAFQSm6YqFL0uyzBPfn6cW9FxnEUyvAr2Z70lK72r00chN3+3PL/azdp iC1r9qg9IKAyL6oYPUDJZLtGt8k8FDKA0ku9VM5w7iOJMyjMwMiK1ubvoLfUX3ncG1ZI KnrzbUPNqgTOYywYRcJMsZDYzljBcv3AIg1xinblw6u0hkAvNuR3+jsP6H1r8QjH2gu9 NY8uAURDdvwAitFsm6/qfSgUyybiHafqRk1LLiz2DNpFs55Jx4CDC+M07FjpofWGorgr LDJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature:dkim-filter; bh=dD91cCsOyIU6CL7hYXVBnV8msJ6UqcWEzTnqgSHYjQE=; b=iqC8rQfG3TeODLYFI7qwP4YKQzSvFWjBoJj8ILn8GRA/65QQmThk+W/jk9KTfLrtZx Meey5cD+m6yss5BDu3Y9NafQ5dkv6bEu1K+NEC3RKt/qYv77KkQLZ+G/owndwq6HCXBl 0EjFzKqLLMt1bMVaObXEK3Pz8mej7Mc837BiPS0L0DIfirjKyKIC/oVduGF6BhQ+qkAp elrvcCBakArQtF32SV987PRLNMdegz4qpjDnPalFcMutvAb3j/0zN1PBN77adrSq7tKR 8faLZAycLG8/MDosKP4idGpzGiS5LiSozxtl4dy+Nb3aZDpupa4PEOzuqYRN7zL48dZg CtbQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=yXI1VxsR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l18si14819402edb.155.2019.09.12.04.53.12; Thu, 12 Sep 2019 04:53:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=yXI1VxsR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731418AbfILLul (ORCPT + 99 others); Thu, 12 Sep 2019 07:50:41 -0400 Received: from conssluserg-04.nifty.com ([210.131.2.83]:51694 "EHLO conssluserg-04.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730923AbfILLul (ORCPT ); Thu, 12 Sep 2019 07:50:41 -0400 Received: from mail-vk1-f175.google.com (mail-vk1-f175.google.com [209.85.221.175]) (authenticated) by conssluserg-04.nifty.com with ESMTP id x8CBoRdw021933; Thu, 12 Sep 2019 20:50:27 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com x8CBoRdw021933 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1568289028; bh=dD91cCsOyIU6CL7hYXVBnV8msJ6UqcWEzTnqgSHYjQE=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=yXI1VxsR0OLXHmqRovjMyeUKTP0L1V0Aw8qZwiWnS7G/WHPvCPawXajV2Ivu3sHka 98x9M+q/8dJBlvhqtaU28qdPigYEQCmLvs075ds09G0Yu6xpCaD/K86wuIa45eeAla 0rW64fQHnGQa845ZKtVqXE5K3Gp65NbxpGNvq6vfywqDcKoXr+HiQ0i5ssW5P0xcRs H9NyghxOOmXXFiZm+q4en7UxVnNvhSoFj3l8P/kdm3DeyQem4Nfn/59jwd9twhBxLu spqh/A19OdA3FdHVPp30hCC4ZmbA9aNZSvpzP1qEDDJwMT0TF2M1eM9PXK81IeGJb0 goE5FZX0uWkmw== X-Nifty-SrcIP: [209.85.221.175] Received: by mail-vk1-f175.google.com with SMTP id d126so5076787vkf.7; Thu, 12 Sep 2019 04:50:27 -0700 (PDT) X-Gm-Message-State: APjAAAXq5Vg9+DA/vfAr2aZu83t223yBJYN4EIFfYcIId3jcgENKkOaS kwi4SHOvmgZGBGz+uF9OHahtCXQBeoNl2vkRWic= X-Received: by 2002:a1f:60c2:: with SMTP id u185mr8154771vkb.0.1568289026492; Thu, 12 Sep 2019 04:50:26 -0700 (PDT) MIME-Version: 1.0 References: <20190907025236.31393-1-yamada.masahiro@socionext.com> In-Reply-To: <20190907025236.31393-1-yamada.masahiro@socionext.com> From: Masahiro Yamada Date: Thu, 12 Sep 2019 20:49:50 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2] kbuild: allow Clang to find unused static inline functions for W=1 build To: Linux Kbuild mailing list Cc: Nick Desaulniers , Nathan Chancellor , Sedat Dilek , Michal Marek , clang-built-linux , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Sep 7, 2019 at 11:53 AM Masahiro Yamada wrote: > > GCC and Clang have different policy for -Wunused-function; GCC does not > warn unused static inline functions at all whereas Clang does if they > are defined in source files instead of included headers although it has > been suppressed since commit abb2ea7dfd82 ("compiler, clang: suppress > warning for unused static inline functions"). > > We often miss to delete unused functions where 'static inline' is used > in *.c files since there is no tool to detect them. Unused code remains > until somebody notices. For example, commit 075ddd75680f ("regulator: > core: remove unused rdev_get_supply()"). > > Let's remove __maybe_unused from the inline macro to allow Clang to > start finding unused static inline functions. For now, we do this only > for W=1 build since it is not a good idea to sprinkle warnings for the > normal build (e.g. 35 warnings for arch/x86/configs/x86_64_defconfig). > > My initial attempt was to add -Wno-unused-function for no W= build > (https://lore.kernel.org/patchwork/patch/1120594/) > > Nathan Chancellor pointed out that would weaken Clang's checks since > we would no longer get -Wunused-function without W=1. It is true GCC > would catch unused static non-inline functions, but it would weaken > Clang as a standalone compiler, at least. > > Hence, here is a counter implementation. The current problem is, W=... > only controls compiler flags, which are globally effective. There is > no way to address only 'static inline' functions. > > This commit defines KBUILD_EXTRA_WARN[123] corresponding to W=[123]. > When KBUILD_EXTRA_WARN1 is defined, __maybe_unused is omitted from > the 'inline' macro. > > The new macro __inline_maybe_unused makes the code a bit uglier, so I > hope we can remove it entirely after fixing most of the warnings. > > If you contribute to code clean-up, please run "make CC=clang W=1" > and check -Wunused-function warnings. You will find lots of unused > functions. > > Some of them are false-positives because the call-sites are disabled > by #ifdef. I do not like to abuse the inline keyword for suppressing > unused-function warnings because it is intended to be a hint for the > compiler optimization. I prefer #ifdef around the definition, or > __maybe_unused if #ifdef would make the code too ugly. > > Signed-off-by: Masahiro Yamada > Reviewed-by: Nathan Chancellor > Tested-by: Nathan Chancellor > --- Applied to linux-kbuild. > > Changes in v2: > - Rebase on top of https://patchwork.kernel.org/patch/11124933/ > > include/linux/compiler_types.h | 20 ++++++++++++++------ > scripts/Makefile.extrawarn | 6 ++++++ > 2 files changed, 20 insertions(+), 6 deletions(-) > > diff --git a/include/linux/compiler_types.h b/include/linux/compiler_types.h > index 599c27b56c29..b056a40116da 100644 > --- a/include/linux/compiler_types.h > +++ b/include/linux/compiler_types.h > @@ -130,10 +130,6 @@ struct ftrace_likely_data { > > /* > * Force always-inline if the user requests it so via the .config. > - * GCC does not warn about unused static inline functions for > - * -Wunused-function. This turns out to avoid the need for complex #ifdef > - * directives. Suppress the warning in clang as well by using "unused" > - * function attribute, which is redundant but not harmful for gcc. > * Prefer gnu_inline, so that extern inline functions do not emit an > * externally visible function. This makes extern inline behave as per gnu89 > * semantics rather than c99. This prevents multiple symbol definition errors > @@ -144,15 +140,27 @@ struct ftrace_likely_data { > */ > #if !defined(CONFIG_OPTIMIZE_INLINING) > #define inline inline __attribute__((__always_inline__)) __gnu_inline \ > - __maybe_unused notrace > + __inline_maybe_unused notrace > #else > #define inline inline __gnu_inline \ > - __maybe_unused notrace > + __inline_maybe_unused notrace > #endif > > #define __inline__ inline > #define __inline inline > > +/* > + * GCC does not warn about unused static inline functions for -Wunused-function. > + * Suppress the warning in clang as well by using __maybe_unused, but enable it > + * for W=1 build. This will allow clang to find unused functions. Remove the > + * __inline_maybe_unused entirely after fixing most of -Wunused-function warnings. > + */ > +#ifdef KBUILD_EXTRA_WARN1 > +#define __inline_maybe_unused > +#else > +#define __inline_maybe_unused __maybe_unused > +#endif > + > /* > * Rather then using noinline to prevent stack consumption, use > * noinline_for_stack instead. For documentation reasons. > diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn > index 53eb7e0c6a5a..ecddf83ac142 100644 > --- a/scripts/Makefile.extrawarn > +++ b/scripts/Makefile.extrawarn > @@ -36,6 +36,8 @@ KBUILD_CFLAGS += $(call cc-option, -Wstringop-truncation) > KBUILD_CFLAGS += -Wno-missing-field-initializers > KBUILD_CFLAGS += -Wno-sign-compare > > +KBUILD_CPPFLAGS += -DKBUILD_EXTRA_WARN1 > + > else > > # Some diagnostics enabled by default are noisy. > @@ -65,6 +67,8 @@ KBUILD_CFLAGS += -Wsign-compare > KBUILD_CFLAGS += $(call cc-option, -Wmaybe-uninitialized) > KBUILD_CFLAGS += $(call cc-option, -Wunused-macros) > > +KBUILD_CPPFLAGS += -DKBUILD_EXTRA_WARN2 > + > endif > > # > @@ -82,4 +86,6 @@ KBUILD_CFLAGS += -Wredundant-decls > KBUILD_CFLAGS += -Wswitch-default > KBUILD_CFLAGS += $(call cc-option, -Wpacked-bitfield-compat) > > +KBUILD_CPPFLAGS += -DKBUILD_EXTRA_WARN3 > + > endif > -- > 2.17.1 > -- Best Regards Masahiro Yamada