Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: [PATCH 0/2] Enable clang tools for kernels build using gcc
To:     Daniel Thompson <daniel.thompson@linaro.org>,
        Nathan Chancellor <nathan@kernel.org>
Cc:     Masahiro Yamada <masahiroy@kernel.org>,
        Michal Marek <michal.lkml@markovi.net>,
        Nick Desaulniers <ndesaulniers@google.com>,
        linux-kbuild@vger.kernel.org, llvm@lists.linux.dev,
        linux-kernel@vger.kernel.org
References: <20220628122741.93641-1-daniel.thompson@linaro.org>
From:   Tom Rix <trix@redhat.com>
Message-ID: <0478d832-d902-69ed-7c1c-4f19d942cddf@redhat.com>
Date:   Tue, 28 Jun 2022 06:19:09 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <20220628122741.93641-1-daniel.thompson@linaro.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk

The limitations of the compilation db are not limited to the kernel.

Why shouldn't the change be made in the llvm project ?

Tom

On 6/28/22 5:27 AM, Daniel Thompson wrote:
> This patch set makes it possible to use clang based tools, such as
> the clangd completion engine, regardless of our choice of compiler
> for the actual kernel build.
>
> Most of the fine details are included in the patch header for the
> first patch (since we'd like them to appear in the kernel history so
> they can help future archaeologists).
>
> Daniel Thompson (2):
>    clang-tools: Generate clang compatible output even with gcc builds
>    Makefile: Enable clang-tidy and clang-analyzer for gcc builds
>
>   Makefile                                    | 11 ++--
>   scripts/clang-tools/gen_compile_commands.py | 71 ++++++++++++++++++++-
>   2 files changed, 74 insertions(+), 8 deletions(-)
>
>
> base-commit: a111daf0c53ae91e71fd2bfe7497862d14132e3e
> --
> 2.35.1
>