[clang] [llvm] [X86] Enhance kCFI type IDs with a 3-bit arity indicator. (PR #117121)
ojeda wrote: > looks like rust is already tracking and willing to support it? > [Rust-for-Linux/linux#1132](https://github.com/Rust-for-Linux/linux/issues/1132) > (thanks @ojeda) You're welcome! Just in case: if the question is about the entry I added today, then that entry is intended to track this PR, the potential consequences/needs for the Rust support in the kernel, related work/links, etc., but it does not imply Rust is tracking it or that they are willing to support it already. https://github.com/llvm/llvm-project/pull/117121 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [llvm] [X86] Extend kCFI with a 3-bit arity indicator (PR #121070)
@@ -254,6 +254,7 @@ FEATURE(is_trivially_constructible, LangOpts.CPlusPlus) FEATURE(is_trivially_copyable, LangOpts.CPlusPlus) FEATURE(is_union, LangOpts.CPlusPlus) FEATURE(kcfi, LangOpts.Sanitize.has(SanitizerKind::KCFI)) +FEATURE(kcfi_x86_arity, LangOpts.Sanitize.has(SanitizerKind::KCFI)) ojeda wrote: For Kconfig, most features are discovered via testing a flag (e.g. `-fsanitize=kcfi`), but if the kernel needs `__has_feature()` anyway here, then that can also be used, yeah. For `rustc`, we can do similar tests too (and since we only support one kind of Rust compiler so far, versions checks can be a fallback option too). https://github.com/llvm/llvm-project/pull/121070 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
