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;
From:   Jani Nikula <jani.nikula@linux.intel.com>
To:     Greg KH <gregkh@linuxfoundation.org>,
        Lukas Bulwahn <lukas.bulwahn@gmail.com>,
        Knut Omang <knut.omang@oracle.com>
Cc:     Ozan Alpay <ozyalpy@gmail.com>,
        Rodrigo Vivi <rodrigo.vivi@intel.com>,
        Ville =?utf-8?B?U3lyasOkbMOk?= <ville.syrjala@linux.intel.com>,
        sil2review@lists.osadl.org, kernelnewbies@kernelnewbies.org,
        David Airlie <airlied@linux.ie>,
        intel-gfx@lists.freedesktop.org,
        Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
        llvmlinux@lists.linuxfoundation.org, linux-kernel@vger.kernel.org,
        dri-devel@lists.freedesktop.org
Subject: Re: clang warning: implicit conversion in intel_ddi.c:1481
In-Reply-To: <20180202100613.GA21492@kroah.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
References: <alpine.DEB.2.20.1802011823340.4316@alpaca> <20180201180240.GA28042@kroah.com> <alpine.DEB.2.20.1802012045570.29994@hsp> <87372jkcu5.fsf@intel.com> <alpine.DEB.2.20.1802021054500.13838@hsp> <20180202100613.GA21492@kroah.com>
Date:   Fri, 02 Feb 2018 12:44:38 +0200
Message-ID: <87h8qzisbt.fsf@intel.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


+Knut, Fengguang

On Fri, 02 Feb 2018, Greg KH <gregkh@linuxfoundation.org> wrote:
> 	- If clang now builds the kernel "cleanly", yes, I want to take
> 	  warning fixes in the stable tree.  And even better yet, if you
> 	  keep working to ensure the tree is "clean", that would be
> 	  wonderful.

So we can run sparse using 'make C=1' and friends, or other static
analysis tools using 'make CHECK=foo C=1', as long as the passed command
line params work. There was work by Knut to extend this make checker
stuff [1]. Since mixing different HOSTCC's in a single workdir seems
like a bad idea, I wonder how hard it would be to make clang work like
this:

$ make CHECK=clang C=1

Or using Knut's wrapper. Feels like that could increase the use of clang
for static analysis of patches.


BR,
Jani.


[1] http://mid.mail-archive.com/cover.5b56d020b8e826a7da33b1823c059acd0c123f8b.1515072782.git-series.knut.omang@oracle.com


-- 
Jani Nikula, Intel Open Source Technology Center