From: Kees Cook <kees@kernel.org>
To: linux-hardening@vger.kernel.org, Christopher Fore <csfore@posteo.net>
Cc: Kees Cook <kees@kernel.org>, linux-kernel@vger.kernel.org
Subject: [PATCH] gcc-plugins: Remove TODO_verify_il for GCC >= 16
Date: Sat, 20 Sep 2025 16:45:23 -0700 [thread overview]
Message-ID: <20250920234519.work.915-kees@kernel.org> (raw)
GCC now runs TODO_verify_il automatically[1], so it is no longer exposed to
plugins. Only use the flag on GCC < 16.
Suggested-by: Christopher Fore <csfore@posteo.net>
Link: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9739ae9384dd7cd3bb1c7683d6b80b7a9116eaf8
Signed-off-by: Kees Cook <kees@kernel.org>
---
How about like this, so it'll still work on GCC <16?
Cc: <linux-hardening@vger.kernel.org>
---
scripts/gcc-plugins/gcc-common.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/scripts/gcc-plugins/gcc-common.h b/scripts/gcc-plugins/gcc-common.h
index 6cb6d1051815..8f1b3500f8e2 100644
--- a/scripts/gcc-plugins/gcc-common.h
+++ b/scripts/gcc-plugins/gcc-common.h
@@ -173,10 +173,17 @@ static inline opt_pass *get_pass_for_id(int id)
return g->get_passes()->get_pass_for_id(id);
}
+#if BUILDING_GCC_VERSION < 16000
#define TODO_verify_ssa TODO_verify_il
#define TODO_verify_flow TODO_verify_il
#define TODO_verify_stmts TODO_verify_il
#define TODO_verify_rtl_sharing TODO_verify_il
+#else
+#define TODO_verify_ssa 0
+#define TODO_verify_flow 0
+#define TODO_verify_stmts 0
+#define TODO_verify_rtl_sharing 0
+#endif
#define INSN_DELETED_P(insn) (insn)->deleted()
--
2.34.1
next reply other threads:[~2025-09-20 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 23:45 Kees Cook [this message]
2025-09-21 16:34 ` [PATCH] gcc-plugins: Remove TODO_verify_il for GCC >= 16 csfore
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=20250920234519.work.915-kees@kernel.org \
--to=kees@kernel.org \
--cc=csfore@posteo.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.