The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: David Binderman <dcb314@hotmail.com>
Cc: "linux-hardening@vger.kernel.org"
	<linux-hardening@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux-6.17 meets gcc trunk
Date: Tue, 30 Sep 2025 09:06:40 -0700	[thread overview]
Message-ID: <202509300859.BF057653FA@keescook> (raw)
In-Reply-To: <VI1PR02MB395284606387C101413494EB9C1AA@VI1PR02MB3952.eurprd02.prod.outlook.com>

On Tue, Sep 30, 2025 at 08:08:27AM +0000, David Binderman wrote:
> Hello there,
> 
> I just tried to compile linux-6.17 with gcc trunk. It said:
> 
>   HDRINST usr/include/asm/types.h
> In file included from scripts/gcc-plugins/latent_entropy_plugin.c:78:
> scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
>   176 | #define TODO_verify_ssa TODO_verify_il
>       |                         ^~~~~~~~~~~~~~
> scripts/gcc-plugins/latent_entropy_plugin.c:567:27: note: in expansion of macro ‘TODO_verify_ssa’
>   567 | #define TODO_FLAGS_FINISH TODO_verify_ssa | TODO_verify_stmts | TODO_dump_func \
>       |                           ^~~~~~~~~~~~~~~
> scripts/gcc-plugins/gcc-generate-gimple-pass.h:86:43: note: in expansion of macro ‘TODO_FLAGS_FINISH’
>    86 |                 .todo_flags_finish      = TODO_FLAGS_FINISH,

This was fixed here:
https://git.kernel.org/linus/a40282dd3c484e6c882e93f4680e0a3ef3814453

It will need backporting to prior kernel releases.

-Kees

-- 
Kees Cook

      reply	other threads:[~2025-09-30 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  8:08 Linux-6.17 meets gcc trunk David Binderman
2025-09-30 16:06 ` Kees Cook [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=202509300859.BF057653FA@keescook \
    --to=kees@kernel.org \
    --cc=dcb314@hotmail.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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