[clang] [Driver] Use empty multilib file in another test (PR #111352)

[via cfe-commits]

llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-clang-driver

Author: Oliver Stannard (ostannard)

<details>
<summary>Changes</summary>

This makes the test independent of the one provided by a toolchain clang is built into, which can cause the output of
-print-multi-flags-experimental to change.

---
Full diff: https://github.com/llvm/llvm-project/pull/111352.diff


1 Files Affected:

- (modified) clang/test/Driver/aarch64-multilib-rcpc3.c (+1-1) 


``````````diff
diff --git a/clang/test/Driver/aarch64-multilib-rcpc3.c b/clang/test/Driver/aarch64-multilib-rcpc3.c
index 88b23de5a65109..5146ec15458fc9 100644
--- a/clang/test/Driver/aarch64-multilib-rcpc3.c
+++ b/clang/test/Driver/aarch64-multilib-rcpc3.c
@@ -1,4 +1,4 @@
-// RUN: %clang --target=aarch64-none-elf -march=armv8.9-a+rcpc3 -print-multi-flags-experimental -c %s 2>&1 | FileCheck %s
+// RUN: %clang --target=aarch64-none-elf -march=armv8.9-a+rcpc3 -print-multi-flags-experimental -multi-lib-config=%S/Inputs/multilib/empty.yaml -c %s 2>&1 | FileCheck %s
 
 // The purpose of this regression test is to make sure that when
 // compile options are converted into multilib selection flags, no

``````````

</details>


https://github.com/llvm/llvm-project/pull/111352