From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master] kbuild: fix clangd warning with GCC compile_commands.json
Date: Wed, 08 Jan 2025 15:32:47 +0100 [thread overview]
Message-ID: <173634676718.75312.6743019876161645064.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250107122426.3713264-1-a.fatoum@pengutronix.de>
On Tue, 07 Jan 2025 13:24:26 +0100, Ahmad Fatoum wrote:
> If barebox is configured to pass -ftrivial-auto-var-init=zero as
> argument to GCC, the compile_commands.json will list it prompting clang
> to complain:
>
> '-ftrivial-auto-var-init=zero' hasn't been enabled; enable it at your own
> peril for benchmarking purpose only with
> '-enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang'
>
> [...]
Applied, thanks!
[1/1] kbuild: fix clangd warning with GCC compile_commands.json
https://git.pengutronix.de/cgit/barebox/commit/?id=2c151ad3fb19 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-01-08 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 12:24 Ahmad Fatoum
2025-01-08 14:32 ` Sascha Hauer [this message]
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=173634676718.75312.6743019876161645064.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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