maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Driver/cuda-output-asm.cu

32 lines
1.5 KiB
Plaintext
Raw Normal View History

Fix bug when compiling CUDA code with -emit-llvm and -o. In this case the device code is not injected into an host action and therefore the user should get an error as -o can't be used when generating two outputs. llvm-svn: 285263
2016-10-27 08:53:34 +08:00
// Tests CUDA compilation with -S and -emit-llvm.
[CUDA] Add test for compiling CUDA code with -S. Reviewers: tra Subscribers: cfe-commits, jhen Differential Revision: http://reviews.llvm.org/D16081 llvm-svn: 257810
2016-01-15 05:41:31 +08:00
// REQUIRES: clang-driver
// REQUIRES: x86-registered-target
// REQUIRES: nvptx-registered-target
// RUN: %clang -### -S -target x86_64-linux-gnu --cuda-gpu-arch=sm_20 %s 2>&1 \
// RUN: | FileCheck -check-prefix HOST -check-prefix SM20 %s
// RUN: %clang -### -S -target x86_64-linux-gnu --cuda-host-only -o foo.s %s 2>&1 \
// RUN: | FileCheck -check-prefix HOST %s
// RUN: %clang -### -S -target x86_64-linux-gnu --cuda-gpu-arch=sm_20 \
// RUN: --cuda-device-only -o foo.s %s 2>&1 \
// RUN: | FileCheck -check-prefix SM20 %s
// RUN: %clang -### -S -target x86_64-linux-gnu --cuda-gpu-arch=sm_20 \
// RUN: --cuda-gpu-arch=sm_30 --cuda-device-only %s 2>&1 \
// RUN: | FileCheck -check-prefix SM20 -check-prefix SM30 %s
// HOST-DAG: "-cc1" "-triple" "x86_64--linux-gnu"
// SM20-DAG: "-cc1" "-triple" "nvptx64-nvidia-cuda"
// SM20-same: "-target-cpu" "sm_20"
// SM30-DAG: "-cc1" "-triple" "nvptx64-nvidia-cuda"
// SM30-same: "-target-cpu" "sm_30"
// RUN: %clang -### -S -target x86_64-linux-gnu -o foo.s %s 2>&1 \
// RUN: | FileCheck -check-prefix MULTIPLE-OUTPUT-FILES %s
// RUN: %clang -### -S -target x86_64-linux-gnu --cuda-device-only \
// RUN: --cuda-gpu-arch=sm_20 --cuda-gpu-arch=sm_30 -o foo.s %s 2>&1 \
// RUN: | FileCheck -check-prefix MULTIPLE-OUTPUT-FILES %s
Fix bug when compiling CUDA code with -emit-llvm and -o. In this case the device code is not injected into an host action and therefore the user should get an error as -o can't be used when generating two outputs. llvm-svn: 285263
2016-10-27 08:53:34 +08:00
// RUN: %clang -### -emit-llvm -c -target x86_64-linux-gnu -o foo.s %s 2>&1 \
// RUN: | FileCheck -check-prefix MULTIPLE-OUTPUT-FILES %s
[CUDA] Add test for compiling CUDA code with -S. Reviewers: tra Subscribers: cfe-commits, jhen Differential Revision: http://reviews.llvm.org/D16081 llvm-svn: 257810
2016-01-15 05:41:31 +08:00
// MULTIPLE-OUTPUT-FILES: error: cannot specify -o when generating multiple output files