From: Tom Rix <trix@redhat.com>
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
Subject: Re: [PATCH 0/2] Enable clang tools for kernels build using gcc
Date: Tue, 28 Jun 2022 06:19:09 -0700 [thread overview]
Message-ID: <0478d832-d902-69ed-7c1c-4f19d942cddf@redhat.com> (raw)
In-Reply-To: <20220628122741.93641-1-daniel.thompson@linaro.org>
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
>
next prev parent reply other threads:[~2022-06-28 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:27 [PATCH 0/2] Enable clang tools for kernels build using gcc Daniel Thompson
2022-06-28 12:27 ` [PATCH 1/2] clang-tools: Generate clang compatible output even with gcc builds Daniel Thompson
2022-06-28 18:35 ` Nick Desaulniers
2022-06-28 12:27 ` [PATCH 2/2] Makefile: Enable clang-tidy and clang-analyzer for " Daniel Thompson
2022-06-28 13:19 ` Tom Rix [this message]
2022-06-28 15:15 ` [PATCH 0/2] Enable clang tools for kernels build using gcc Daniel Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0478d832-d902-69ed-7c1c-4f19d942cddf@redhat.com \
--to=trix@redhat.com \
--cc=daniel.thompson@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox