================ @@ -0,0 +1,143 @@ +// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py UTC_ARGS: --version 6 +// REQUIRES: aarch64-registered-target + +// RUN: %clang_cc1 -triple aarch64 -target-feature +sve -disable-O0-optnone -Werror -Wall -fclangir -emit-cir -o - %s | FileCheck %s --check-prefixes=ALL,CIR +// RUN: %clang_cc1 -DSVE_OVERLOADED_FORMS -triple aarch64 -target-feature +sve -disable-O0-optnone -Werror -Wall -fclangir -emit-cir -o - %s | FileCheck %s --check-prefixes=ALL,CIR +// +// RUN: %clang_cc1 -triple aarch64 -target-feature +sve -disable-O0-optnone -Werror -Wall -fclangir -emit-llvm -o - %s | FileCheck %s --check-prefixes=ALL,LLVM +// RUN: %clang_cc1 -DSVE_OVERLOADED_FORMS -triple aarch64 -target-feature +sve -disable-O0-optnone -Werror -Wall -fclangir -emit-llvm -o - %s | FileCheck %s --check-prefixes=ALL,LLVM ---------------- banach-space wrote:
Yes! On a related note, I feel that it could be helpful to create some common PyThon substitutions for these very long invocation lines. For example: ```PyThon %clang_cc1_llvm_c = %clang_cc1 -disable-O0-optnone -Werror -Wall -fclangir -emit-llvm -o - %s ``` And then: ```c //RUN: %clang_cc1_llvm_c -triple aarch64 -target-feature +sve | FileCheck %s --check-prefixes=ALL,LLVM ``` Or something similar that would make it clearer (and more visible) what the difference between different `RUN` lines is. https://github.com/llvm/llvm-project/pull/172346 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
