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;
From:   Thomas Gleixner <tglx@linutronix.de>
To:     suhui_kernel@163.com, mingo@kernel.org
Cc:     akpm@linux-foundation.org, bp@alien8.de, dietmar.eggemann@arm.com,
        juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
        luto@amacapital.net, mgorman@suse.de, peterz@infradead.org,
        torvalds@linux-foundation.org, vincent.guittot@linaro.org,
        nhuck@google.com, ndesaulniers@google.com, lukas.bulwahn@gmail.com,
        masahiroy@kernel.org
Subject: Re: [PATCH 09/15] sched/headers: Introduce
 kernel/sched/build_policy.c and build multiple .c files there
In-Reply-To: <20220823074702.2900118-1-suhui_kernel@163.com>
References: <20220315084247.40783-10-mingo@kernel.org>
 <20220823074702.2900118-1-suhui_kernel@163.com>
Date:   Wed, 24 Aug 2022 17:50:02 +0200
Message-ID: <87pmgpy72t.ffs@tglx>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

On Tue, Aug 23 2022 at 15:47, suhui kernel wrote:
> Hi Ingo, Since commit f96eca432015ddc1b621632488ebc345bca06791 merged, the
> scripts/clang-tools/gen_compile_commands.py can't work very well.
>
>   In this patch the build_policy.c and build_utility.c include kernel/sched/xxx.c(
> such as rt.c idle.c...), so it compile the build_utility.o build_policy.o directly,
> and it won't generate kernel/sched/xxx.c(such as rt.o idle.o), so the gen_compile_commands.py
> can't work.

gen_compile_commands.py works perfectly fine and generates the entries
for build_policy.o and built_utility.o as expected.

gen_compile_commands.py scans the build tree for .cmd files and extracts
the command line from those files into the the json file. As there is no
.cmd file for the .c files which are included into build_*.c there wont
be entries in the json file either.

>   It will report "[8/23/2022, 3:24:06 PM] "rt.c" not found in "${workspaceFolder}/compile_commands.json".
> 'includePath' from c_cpp_properties.json in folder 'linux' will be
> used for this file instead.".

No idea where this message comes from, but certainly not from
gen_compile_commands.py because that generates the file.

The clang-tidy kernel build target generates and uses that file and that
works perfectly fine.

So what exactly broke?

Thanks,

        tglx