Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1339242imm; Wed, 20 Jun 2018 16:20:19 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLxZOq/0Sz0Pvu8ShJNVsLuWiXnqQ9kQcEydOHbqvIBXZ81rom4C0KGsethu0tQiGb77Ez3 X-Received: by 2002:a65:4cc3:: with SMTP id n3-v6mr20127864pgt.98.1529536819180; Wed, 20 Jun 2018 16:20:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529536819; cv=none; d=google.com; s=arc-20160816; b=r+Q0Xl/jLe5wrqyrtdCa784FOL7boRylNQs2eCTqVgJQ7ryTpBxsfOcYCKeBoGTqK7 Vr2o9z/h2A3SQ1jcTtaqoI/cMJBK35oWNehlY5fg42V6fCAhOVAbuMdGN+XEgEwz3EzK SYAbLPrsNPQQEtHCAGRV6MPnXDm4cqdeKC0K5ZXqLF3UPg0k/HprQ1NmzRoypsCUsByb tXe8ElBE3xtwGFUdT7l+KGIGzjdjUH2GIFff49aH8rZE5e7OYK+77MsLJlvGGAxW0s3N jO436nRNk/ONV9O1wanoHD/zmNW2mhN9jko7Fazn6LFbR4JQd//hGV6YwtyZcA9qHQ7X JOgw== 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 :references:in-reply-to:mime-version:dkim-signature:dkim-filter :arc-authentication-results; bh=9vrsGmZqC+GEIrYCahrSYjjvsiH/Pb/HRSGorzhJ1AY=; b=A8vF2UYcF+yKLVZwA4hdXXtuFGWCKyP70kUzS9YzO87HEJVIWDnG+sn1Rzy2gJKJ5P i9ewp6Xac40x4FbEwAb4WuNNFm/nIAFkT5eKvMaD/MLcK/8GUVu31vuljA2Rm6r8NHz6 jw1sHW/Z1Hquoh6rUdAM0cp8eh89D919szByk0jzEeX4SFWGFKyoTgAQPLsTqrarayCl vYn4M2z0/Bi+iF3mkxhfbTxQzYleoCvk/MKjTRUxrKtsX/Lkfdt9/ycNZAkoSxHQ0F2z CWAwrczeBwK2FP9n7upxU3Ir3+t+hFoW8hv9nRjj7/cWYlULCrR+yK9kHiP3ryggWjW6 uEcA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=zhCJSGvf; 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 a7-v6si2863552pgc.125.2018.06.20.16.20.04; Wed, 20 Jun 2018 16:20:19 -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=zhCJSGvf; 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 S1754339AbeFTXSS (ORCPT + 99 others); Wed, 20 Jun 2018 19:18:18 -0400 Received: from conssluserg-01.nifty.com ([210.131.2.80]:31399 "EHLO conssluserg-01.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754129AbeFTXSQ (ORCPT ); Wed, 20 Jun 2018 19:18:16 -0400 Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com [209.85.213.47]) (authenticated) by conssluserg-01.nifty.com with ESMTP id w5KNI1HX027214; Thu, 21 Jun 2018 08:18:02 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com w5KNI1HX027214 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1529536682; bh=9vrsGmZqC+GEIrYCahrSYjjvsiH/Pb/HRSGorzhJ1AY=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=zhCJSGvfo9vi9wMXx0u5ghhHeRZfuqFlxzWjEVgauLZrTB9bvixTQ/JsJVFh4yEBE THX1XqyY+0eOjHiG4axupQzIseA5fWyd7SAQUXU4MvsHnxDcPWKDuNJYTRhfDRFyO6 rH1iLrZl++HF7UE/z7LYtAzRpdyZBC/1gpD+tEYP6fIeUcQvBud5kgvb08NWCxViUT NkJJ23l3o9w7lO+sH9gLINbN2Y4P1wAvdFFpJt8SsAncXxXNf/KhdYCGw5oyUpnfRC uLPf6H+fxqDFuugnHyQCD78D2IMT1zOgmDOaV65EYz/Z88TiISFeMEilyAB8+OCidJ VGGv1z3vx1RUA== X-Nifty-SrcIP: [209.85.213.47] Received: by mail-vk0-f47.google.com with SMTP id b77-v6so767473vkb.5; Wed, 20 Jun 2018 16:18:02 -0700 (PDT) X-Gm-Message-State: APt69E2RBg2S9fTTSJKxdZ+IB5fQcz+VN1OrcydRyxfavkcMHZkAa0P0 Q+YYDN0xX6tDCJnRwVRKw+s2B1L4hixVexbySYM= X-Received: by 2002:a1f:c944:: with SMTP id z65-v6mr13516653vkf.11.1529536681104; Wed, 20 Jun 2018 16:18:01 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:1ec1:0:0:0:0:0 with HTTP; Wed, 20 Jun 2018 16:17:18 -0700 (PDT) In-Reply-To: <20180619201458.4559-2-paul.burton@mips.com> References: <20180619190225.7eguhiw3ixaiwpgl@pburton-laptop> <20180619201458.4559-1-paul.burton@mips.com> <20180619201458.4559-2-paul.burton@mips.com> From: Masahiro Yamada Date: Thu, 21 Jun 2018 08:17:18 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 1/3] kbuild: add macro for controlling warnings to linux/compiler.h To: Paul Burton Cc: Linux Kbuild mailing list , Mauro Carvalho Chehab , Linux-MIPS , Arnd Bergmann , Ingo Molnar , Matthew Wilcox , Thomas Gleixner , Douglas Anderson , Josh Poimboeuf , Andrew Morton , Matthias Kaehlcke , He Zhe , Benjamin Herrenschmidt , Michal Marek , Khem Raj , Christophe Leroy , Al Viro , Stafford Horne , Gideon Israel Dsouza , Kees Cook , Michael Ellerman , Heiko Carstens , Linux Kernel Mailing List , Paul Mackerras , linuxppc-dev 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 Hi. 2018-06-20 5:14 GMT+09:00 Paul Burton : > From: Arnd Bergmann > > I have occasionally run into a situation where it would make sense to > control a compiler warning from a source file rather than doing so from > a Makefile using the $(cc-disable-warning, ...) or $(cc-option, ...) > helpers. > > The approach here is similar to what glibc uses, using __diag() and > related macros to encapsulate a _Pragma("GCC diagnostic ...") statement > that gets turned into the respective "#pragma GCC diagnostic ..." by > the preprocessor when the macro gets expanded. > > Like glibc, I also have an argument to pass the affected compiler > version, but decided to actually evaluate that one. For now, this > supports GCC_4_6, GCC_4_7, GCC_4_8, GCC_4_9, GCC_5, GCC_6, GCC_7, > GCC_8 and GCC_9. Adding support for CLANG_5 and other interesting > versions is straightforward here. GNU compilers starting with gcc-4.2 > could support it in principle, but "#pragma GCC diagnostic push" > was only added in gcc-4.6, so it seems simpler to not deal with those > at all. The same versions show a large number of warnings already, > so it seems easier to just leave it at that and not do a more > fine-grained control for them. > > The use cases I found so far include: > > - turning off the gcc-8 -Wattribute-alias warning inside of the > SYSCALL_DEFINEx() macro without having to do it globally. > > - Reducing the build time for a simple re-make after a change, > once we move the warnings from ./Makefile and > ./scripts/Makefile.extrawarn into linux/compiler.h > > - More control over the warnings based on other configurations, > using preprocessor syntax instead of Makefile syntax. This should make > it easier for the average developer to understand and change things. > > - Adding an easy way to turn the W=1 option on unconditionally > for a subdirectory or a specific file. This has been requested > by several developers in the past that want to have their subsystems > W=1 clean. > > - Integrating clang better into the build systems. Clang supports > more warnings than GCC, and we probably want to classify them > as default, W=1, W=2 etc, but there are cases in which the > warnings should be classified differently due to excessive false > positives from one or the other compiler. > > - Adding a way to turn the default warnings into errors (e.g. using > a new "make E=0" tag) while not also turning the W=1 warnings into > errors. > > This patch for now just adds the minimal infrastructure in order to > do the first of the list above. As the #pragma GCC diagnostic > takes precedence over command line options, the next step would be > to convert a lot of the individual Makefiles that set nonstandard > options to use __diag() instead. > > [paul.burton@mips.com: > - Rebase atop current master. > - Add __diag_GCC, or more generally __diag_, abstraction to > avoid code outside of linux/compiler-gcc.h needing to duplicate > knowledge about different GCC versions. > - Add a comment argument to __diag_{ignore,warn,error} which isn't > used in the expansion of the macros but serves to push people to > document the reason for using them - per feedback from Kees Cook. > - Translate severity to GCC-specific pragmas in linux/compiler-gcc.h > rather than using GCC-specific in linux/compiler_types.h. > - Drop all but GCC 8 macros, since we only need to define macros for > versions that we need to introduce pragmas for, and as of this > series that's just GCC 8. > - Capitalize comments in linux/compiler-gcc.h to match the style of > the rest of the file. > - Line up macro definitions with tabs in linux/compiler-gcc.h.] > > Signed-off-by: Arnd Bergmann > Signed-off-by: Paul Burton > Tested-by: Christophe Leroy > Tested-by: Stafford Horne > Cc: Michal Marek > Cc: Masahiro Yamada > Cc: Douglas Anderson > Cc: Al Viro > Cc: Heiko Carstens > Cc: Mauro Carvalho Chehab > Cc: Matthew Wilcox > Cc: Matthias Kaehlcke > Cc: Arnd Bergmann > Cc: Ingo Molnar > Cc: Josh Poimboeuf > Cc: Kees Cook > Cc: Andrew Morton > Cc: Thomas Gleixner > Cc: Gideon Israel Dsouza > Cc: Christophe Leroy > Cc: Benjamin Herrenschmidt > Cc: Paul Mackerras > Cc: Michael Ellerman > Cc: Stafford Horne > Cc: Khem Raj > Cc: He Zhe > Cc: linux-kbuild@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Cc: linux-mips@linux-mips.org > Cc: linuxppc-dev@lists.ozlabs.org > > --- > > Changes in v2: > - Add version argument to fallback __diag_GCC definition. > - Translate severity from generic ignore,warn,error to GCC-specific > pragma content ignored,warning,error in linux/compiler-gcc.h in order > to keep linux/compiler_types.h generic per feedback from Masahiro > Yamada. > - Drop all but GCC 8 macros, since we only need to define macros for > versions that we need to introduce pragmas for, and as of this series > that's just GCC 8. > - Capitalize comments in linux/compiler-gcc.h to match the style of the > rest of the file. > - Line up macro definitions with tabs in linux/compiler-gcc.h. > > include/linux/compiler-gcc.h | 27 +++++++++++++++++++++++++++ > include/linux/compiler_types.h | 18 ++++++++++++++++++ > 2 files changed, 45 insertions(+) > > diff --git a/include/linux/compiler-gcc.h b/include/linux/compiler-gcc.h > index f1a7492a5cc8..5067a90af9c3 100644 > --- a/include/linux/compiler-gcc.h > +++ b/include/linux/compiler-gcc.h > @@ -347,3 +347,30 @@ > #if GCC_VERSION >= 50100 > #define COMPILER_HAS_GENERIC_BUILTIN_OVERFLOW 1 > #endif > + > +/* > + * Turn individual warnings and errors on and off locally, depending > + * on version. > + */ > +#define __diag_GCC(version, severity, s) \ > + __diag_GCC_ ## version(__diag_GCC_ ## severity s) > + > +/* Severity used in pragma directives */ > +#define __diag_GCC_ignore ignored > +#define __diag_GCC_warn warning > +#define __diag_GCC_error error > + > +/* Compilers before gcc-4.6 do not understand "#pragma GCC diagnostic push" */ > +#if GCC_VERSION >= 40600 > +#define __diag_str1(s) #s > +#define __diag_str(s) __diag_str1(s) > +#define __diag(s) _Pragma(__diag_str(GCC diagnostic s)) > +#else > +#define __diag(s) You can omit the #else here because it is covered by compiler_types.h > +#endif > + > +#if GCC_VERSION >= 80000 > +#define __diag_GCC_8(s) __diag(s) > +#else > +#define __diag_GCC_8(s) > +#endif > diff --git a/include/linux/compiler_types.h b/include/linux/compiler_types.h > index 6b79a9bba9a7..a8ba6b04152c 100644 > --- a/include/linux/compiler_types.h > +++ b/include/linux/compiler_types.h > @@ -271,4 +271,22 @@ struct ftrace_likely_data { > # define __native_word(t) (sizeof(t) == sizeof(char) || sizeof(t) == sizeof(short) || sizeof(t) == sizeof(int) || sizeof(t) == sizeof(long)) > #endif > > +#ifndef __diag > +#define __diag(string) > +#endif > + > +#ifndef __diag_GCC > +#define __diag_GCC(version, severity, string) > +#endif > + > +#define __diag_push() __diag(push) > +#define __diag_pop() __diag(pop) > + > +#define __diag_ignore(compiler, version, option, comment) \ > + __diag_ ## compiler(version, ignore, option) > +#define __diag_warn(compiler, version, option, comment) \ > + __diag_ ## compiler(version, warn, option) > +#define __diag_error(compiler, version, option, comment) \ > + __diag_ ## compiler(version, error, option) > + > #endif /* __LINUX_COMPILER_TYPES_H */ > -- > 2.17.1 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Masahiro Yamada