
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.
25 lines
707 B
LLVM
25 lines
707 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 -verify-machineinstrs | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 -verify-machineinstrs | %ptxas-verify %}
|
|
|
|
target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64"
|
|
|
|
; CHECK: .visible .func (.param .b32 func_retval0) callee
|
|
define i8 @callee(i8 %a) {
|
|
; CHECK: ld.param.b8
|
|
%ret = add i8 %a, 42
|
|
; CHECK: st.param.b32
|
|
ret i8 %ret
|
|
}
|
|
|
|
; CHECK: .visible .func caller
|
|
define void @caller(ptr %a) {
|
|
; CHECK: ld.b8
|
|
%val = load i8, ptr %a
|
|
%ret = tail call i8 @callee(i8 %val)
|
|
; CHECK: ld.param.b32
|
|
store i8 %ret, ptr %a
|
|
ret void
|
|
}
|
|
|
|
|