maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/polly/test/GPGPU/scalar-parameter-i128.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.1 KiB
LLVM
Raw Normal View History

[test] Do not emit binary data to output Suggested-by: Michael Kruse <llvm@meinersbur.de> llvm-svn: 296852
2017-03-03 11:24:34 +08:00
; RUN: opt %loadPolly -polly-codegen-ppcg -polly-acc-dump-code -disable-output %s
GPGPU: Generate PTX assembly code for the kernel modules Run the NVPTX backend over the GPUModule IR and write the resulting assembly code in a string. To work correctly, it is important to invalidate analysis results that still reference the IR in the kernel module. Hence, this change clears all references to dominators, loop info, and scalar evolution. Finally, the NVPTX backend has troubles to generate code for various special floating point types (not surprising), but also for uncommon integer types. This commit does not resolve these issues, but pulls out problematic test cases into separate files to XFAIL them individually and resolve them in future (not immediate) changes one by one. llvm-svn: 276396
2016-07-22 15:11:12 +08:00
; XFAIL: *
[tests] Specify the dependence to NVPTX backend for Polly ACC test cases Some Polly ACC test cases fail without a working NVPTX backend. We explicitly specify this dependence in REQUIRES. Alternatively, we could have only marked polly-acc as supported in case the NVPTX backend is available, but as we might use other backends in the future, this does not seem to be the best choice. For this to work, we also need to make the 'targets_to_build' information available. Suggested-by: Michael Kruse <llvm@meinersbur.de> llvm-svn: 296853
2017-03-03 11:38:50 +08:00
; REQUIRES: pollyacc,nvptx
GPGPU: Generate PTX assembly code for the kernel modules Run the NVPTX backend over the GPUModule IR and write the resulting assembly code in a string. To work correctly, it is important to invalidate analysis results that still reference the IR in the kernel module. Hence, this change clears all references to dominators, loop info, and scalar evolution. Finally, the NVPTX backend has troubles to generate code for various special floating point types (not surprising), but also for uncommon integer types. This commit does not resolve these issues, but pulls out problematic test cases into separate files to XFAIL them individually and resolve them in future (not immediate) changes one by one. llvm-svn: 276396
2016-07-22 15:11:12 +08:00
; This fails today with "LowerFormalArguments didn't emit the correct number of
; values!"
; void foo(i128 A[], i128 b) {
; for (long i = 0; i < 1024; i++)
; A[i] += b;
; }
;
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
define void @i128(i128* %A, i128 %b) {
bb:
br label %bb1
bb1: ; preds = %bb5, %bb
%i.0 = phi i128 [ 0, %bb ], [ %tmp6, %bb5 ]
%exitcond = icmp ne i128 %i.0, 1024
br i1 %exitcond, label %bb2, label %bb7
bb2: ; preds = %bb1
%tmp = getelementptr inbounds i128, i128* %A, i128 %i.0
%tmp3 = load i128, i128* %tmp, align 4
%tmp4 = add i128 %tmp3, %b
store i128 %tmp4, i128* %tmp, align 4
br label %bb5
bb5: ; preds = %bb2
%tmp6 = add nuw nsw i128 %i.0, 1
br label %bb1
bb7: ; preds = %bb1
ret void
}