================
@@ -12,7 +12,10 @@
! RUN: %flang -### --target=x86_64-unknown-haiku %S/Inputs/hello.f90 2>&1 |
FileCheck %s --check-prefixes=CHECK,HAIKU,HAIKU-F128%f128-lib
! RUN: %flang -### --target=x86_64-windows-gnu %S/Inputs/hello.f90 2>&1 |
FileCheck %s --check-prefixes=CHECK,MINGW,MINGW-F128%f128-lib
-! RUN: %flang -### -rtlib=compiler-rt --target=aarch64-linux-gnu
%S/Inputs/hello.f90 2>&1 | FileCheck %s --check-prefixes=CHECK,UNIX,COMPILER-RT
+! RUN: %flang -### -rtlib=compiler-rt --target=aarch64-linux-gnu
%S/Inputs/hello.f90 > %t 2>&1
+! RUN: FileCheck %s --input-file=%t --check-prefixes=CHECK,UNIX,COMPILER-RT
+! RUN: FileCheck %s --input-file=%t --check-prefix=NO-LIBGCC-BUILTINS
+! RUN: FileCheck %s --input-file=%t --check-prefix=%if
default-unwindlib=libgcc %{DEFAULT-UNWIND-LIBGCC%} %else
%{DEFAULT-UNWIND-NO-LIBGCC%}
----------------
tarunprabhu wrote:
Do we need to know exactly which default unwind library was used? What if the
default unwind library is not libgcc? Is it possible to specify
`CLANG_DEFAULT_UNWINDLIB=foo`? If so, we should be checking that `foo` appears
here. I am not sure if it is possible to do that with the current FileCheck
mechanisms. If it is not, it should be ok to not run this test if
`CLANG_DEFAULT_UNWINDLIB` is set.
https://github.com/llvm/llvm-project/pull/212419
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
