369891b674
In most cases, the type information attached to load and store instructions is meaningless and inconsistently applied. We can usually use ".b" loads and avoid the complexity of trying to assign the correct type. The one expectation is sign-extending load, which will continue to use ".s" to ensure the sign extension into a larger register is done correctly.
26 lines
658 B
LLVM
26 lines
658 B
LLVM
; RUN: llc < %s | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s | %ptxas-verify %}
|
|
|
|
target triple = "nvptx64-nvidia-cuda"
|
|
|
|
declare void @foo()
|
|
|
|
; Load a value, then call a function. Branch, and use the loaded value only on
|
|
; one side of the branch. The load shouldn't be sunk beneath the call, because
|
|
; the call may modify memory.
|
|
define i32 @f(i32 %x, ptr %ptr, i1 %cond) {
|
|
Start:
|
|
; CHECK: ld.b32
|
|
%ptr_val = load i32, ptr %ptr
|
|
; CHECK: call.uni
|
|
call void @foo()
|
|
br i1 %cond, label %L1, label %L2
|
|
L1:
|
|
%ptr_val2 = add i32 %ptr_val, 100
|
|
br label %L2
|
|
L2:
|
|
%v4 = phi i32 [ %x, %Start ], [ %ptr_val2, %L1 ]
|
|
%v5 = add i32 %v4, 1000
|
|
ret i32 %v5
|
|
}
|