================ @@ -104,6 +104,7 @@ FEATURE(thread_sanitizer, LangOpts.Sanitize.has(SanitizerKind::Thread)) FEATURE(dataflow_sanitizer, LangOpts.Sanitize.has(SanitizerKind::DataFlow)) FEATURE(scudo, LangOpts.Sanitize.hasOneOf(SanitizerKind::Scudo)) FEATURE(ptrauth_intrinsics, LangOpts.PointerAuthIntrinsics) +FEATURE(ptrauth_qualifier, LangOpts.PointerAuthIntrinsics) ---------------- AaronBallman wrote:
It does not, see the top of `Features.def`: ``` // FEATURE(...) should be used to advertise support for standard language // features, whereas EXTENSION(...) should be used for clang extensions. Note // that many of the identifiers in this file don't follow this rule for backward // compatibility reasons. ``` Those backwards compatibility reasons are from a time when we only had one way to feature test macros. I think those internal projects should migrate to the correct usage instead of adding this as `FEATURE` for all uses moving forward. https://github.com/llvm/llvm-project/pull/100830 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
