[clang] [clang] Fix ARM64X driver checks for in-process cc1 (PR #240278)
via cfe-commits
cfe-commits at lists.llvm.org
Sun Nov 8 22:42:59 PST 2026
llvmorg-github-actions[bot] wrote:
<!--LLVM PR SUMMARY COMMENT-->
@llvm/pr-subscribers-clang-driver
Author: Anutosh Bhat (anutosh491)
<details>
<summary>Changes</summary>
I missed updating `arm64x.c` in #<!-- -->222531. It uses `CHECK-NEXT` between the two cc1 commands, but in-process execution now prints `(in-process)` between them, causing the Fuchsia buildbot failure.
This adjusts the check and adds explicit coverage for both cc1 modes. Both pass locally. Could we take this small test-only follow-up without reverting and relanding #<!-- -->222531?
---
Full diff: https://github.com/llvm/llvm-project/pull/240278.diff
1 Files Affected:
- (modified) clang/test/Driver/arm64x.c (+3-1)
``````````diff
diff --git a/clang/test/Driver/arm64x.c b/clang/test/Driver/arm64x.c
index f2c187cc1cfce9..d17bcb438a87a2 100644
--- a/clang/test/Driver/arm64x.c
+++ b/clang/test/Driver/arm64x.c
@@ -2,7 +2,9 @@
// RUN: %clang -c -marm64x --target=arm64ec-pc-windows-gnu -### %s 2>&1 | FileCheck %s
// RUN: %clang -c -marm64x --target=aarch64-pc-windows-msvc -### %s 2>&1 | FileCheck %s
// RUN: %clang -c -marm64x --target=aarch64-pc-windows-gnu -### %s 2>&1 | FileCheck %s
+// RUN: %clang -fintegrated-cc1 -c -marm64x --target=arm64ec-pc-windows-msvc -### %s 2>&1 | FileCheck %s
+// RUN: %clang -fno-integrated-cc1 -c -marm64x --target=arm64ec-pc-windows-msvc -### %s 2>&1 | FileCheck %s
// CHECK: "-cc1" "-triple" "aarch64-pc-windows-{{.*}}" "-emit-obj"
-// CHECK-NEXT: "-cc1" "-triple" "arm64ec-pc-windows-{{.*}}" "-emit-obj"
+// CHECK: "-cc1" "-triple" "arm64ec-pc-windows-{{.*}}" "-emit-obj"
// CHECK-NEXT: llvm-objcopy" "--add-section=.obj.arm64ec={{.*}}arm64x-arm64ec-{{.*}}.o" "--set-section-flags=.obj.arm64ec=exclude" "{{.*}}arm64x-aarch64-{{.*}}.o" "arm64x.o"
``````````
</details>
https://github.com/llvm/llvm-project/pull/240278
More information about the cfe-commits
mailing list