================ @@ -46,9 +46,9 @@ // ARM64X: "-machine:arm64x" // RUN: not %clang --target=x86_64-linux-gnu -marm64x -### %s 2>&1 | FileCheck --check-prefix=HYBRID-ERR %s -// HYBRID-ERR: error: unsupported option '-marm64x' for target 'x86_64-linux-gnu' +// HYBRID-ERR: error: unsupported option '-marm64x' for target 'x86_64-unknown-linux-gnu' -// RUN: %clang -c -marm64x --target=arm64ec-pc-windows-msvc -fuse-ld=link -### %s 2>&1 | \ +// RUN: %clang -S -marm64x --target=arm64ec-pc-windows-msvc -fuse-ld=link -### %s 2>&1 | \ ---------------- mstorsjo wrote:
Oh, so for an `-S` compile job, we don't invoke the multi-arch logic at all? I presume the same holds for darwin targets as well then? https://github.com/llvm/llvm-project/pull/207612 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
