[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0478d832-d902-69ed-7c1c-4f19d942cddf@redhat.com>
Date: Tue, 28 Jun 2022 06:19:09 -0700
From: Tom Rix <trix@...hat.com>
To: Daniel Thompson <daniel.thompson@...aro.org>,
Nathan Chancellor <nathan@...nel.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nick Desaulniers <ndesaulniers@...gle.com>,
linux-kbuild@...r.kernel.org, llvm@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Enable clang tools for kernels build using gcc
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
>
Powered by blists - more mailing lists