[clang] [clang] Fix ARM64X driver checks for in-process cc1 (PR #240278)
Anutosh Bhat via cfe-commits
cfe-commits at lists.llvm.org
Sun Nov 8 22:42:18 PST 2026
https://github.com/anutosh491 created https://github.com/llvm/llvm-project/pull/240278
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?
>From 1960adb1c0e3272a38bf1c92302c99f9b4842921 Mon Sep 17 00:00:00 2001
From: anutosh491 <andersonbhat491 at gmail.com>
Date: Mon, 9 Nov 2026 12:10:46 +0530
Subject: [PATCH] [clang] Fix ARM64X driver checks for in-process cc1
---
clang/test/Driver/arm64x.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
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"
More information about the cfe-commits
mailing list