================
@@ -311,3 +311,19 @@
// CHECK-X86_64-GCC: Found candidate GCC installation:
{{.*}}i686-linux-android{{[/\\]}}4.9
// CHECK-X86_64-GCC-NEXT: Found candidate GCC installation:
{{.*}}x86_64-linux-android{{[/\\]}}4.9
// CHECK-X86_64-GCC-NEXT: Selected GCC installation:
{{.*}}x86_64-linux-android{{[/\\]}}4.9
+//
+// RUN: %clang -### %s 2>&1 \
+// RUN: --target=riscv64-linux-android \
+// RUN: -march=rv64i \
+// RUN: --gcc-toolchain=%S/Inputs/basic_android_ndk_tree \
----------------
DanAlbert wrote:
The `CHECK-ARM64` variant of the test has it. I think it's so the test can find
the linker? As long as this test is essentially a copy of that with the target
and arch names swapped out, it's at least not wronger than the existing tests.
https://github.com/llvm/llvm-project/pull/116892
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
