[clang] [clang][AArch64] test -cc1 -print-enabled-extensions (PR #143570)

2025-06-11 Thread Alexandros Lamprineas via cfe-commits
https://github.com/labrinea approved this pull request. We can debate on what the sensible behavior ought to be, but I agree having a test in place to show the current behavior is a good idea. Thanks for writing one. https://github.com/llvm/llvm-project/pull/143570

[clang] [clang][AArch64] test -cc1 -print-enabled-extensions (PR #143570)

2025-06-10 Thread David Green via cfe-commits
https://github.com/davemgreen approved this pull request. https://github.com/llvm/llvm-project/pull/143570 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [clang][AArch64] test -cc1 -print-enabled-extensions (PR #143570)

2025-06-10 Thread via cfe-commits
llvmbot wrote: @llvm/pr-subscribers-clang Author: Tomas Matheson (tmatheson-arm) Changes This adds tests that document how -cc1 and -print-enabled-extensions interact. The current behaviour looks wrong, and is caused by the fact that --print-enabled-extensions uses the MC subtarget featu

[clang] [clang][AArch64] test -cc1 -print-enabled-extensions (PR #143570)

2025-06-10 Thread Tomas Matheson via cfe-commits
https://github.com/tmatheson-arm created https://github.com/llvm/llvm-project/pull/143570 This adds tests that document how -cc1 and -print-enabled-extensions interact. The current behaviour looks wrong, and is caused by the fact that --print-enabled-extensions uses the MC subtarget feature AP