[lkml]   [2019]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH] kbuild: Add option to generate a Compilation Database
On Thu, Jun 6, 2019 at 1:54 PM Tom Roeder <> wrote:
> On Thu, Jun 06, 2019 at 02:30:03PM -0600, Raul E Rangel wrote:
> > Clang tooling requires a compilation database to figure out the build
> > options for each file. This enables tools like clang-tidy and
> > clang-check.
> >
> > See for more
> > information.

I'm also super happy to see this!
I don't know enough about GNU Make/Kbuild to answer the questions, but
hopefully Masahiro can help there.

> I'm glad to see someone adding this to the Makefile directly. I added
> scripts/ in b302046 (in Dec 2018) when I was

Heh, cool. I had a script that basically did this; we recently
dropped it from the Android trees when doing an audit of out of tree

> working on using clang-check to look for bugs in KVM. That script

I'm very interested in this work; my summer intern is looking into
static analyses of the Linux kernel. Can you maybe reach out to me
off thread to tell me more about what you found (or didn't)?

> > Normally cmake is used to generate the compilation database, but the
> > linux kernel uses make. Another option is using
> > [BEAR]( which instruments
> > exec to find clang invocations and generate the database that way.

It's probably possible to get this to work w/ GCC if the additional
dependency of bear exists on the host's system (and may reduce the
number of implementations). Downside is the additional host

Sounds like it may also be possible to just run
scripts/ at build time if this config is

Maybe a comparison of the output of Tom's script and your patch might
reveal if one approach is incomplete?
~Nick Desaulniers

 \ /
  Last update: 2019-06-07 01:40    [W:0.088 / U:19.412 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site