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.
25 lines
801 B
LLVM
25 lines
801 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 | FileCheck %s
|
|
|
|
%st = type { i8, i8, i16 }
|
|
|
|
@a = internal addrspace(1) global %st zeroinitializer, align 8
|
|
@b = internal addrspace(1) global i32 0, align 8
|
|
@c = internal addrspace(1) global i32 0, align 8
|
|
|
|
; Verify that loads with different memory types are not subject to CSE
|
|
; once they are promoted to the same type.
|
|
;
|
|
; CHECK: ld.global.v2.b8 {%[[B1:rs[0-9]+]], %[[B2:rs[0-9]+]]}, [a];
|
|
; CHECK: st.global.v2.b8 [b], {%[[B1]], %[[B2]]};
|
|
;
|
|
; CHECK: ld.global.b32 %[[C:r[0-9]+]], [a];
|
|
; CHECK: st.global.b32 [c], %[[C]];
|
|
|
|
define void @test1() #0 {
|
|
%1 = load <2 x i8>, ptr addrspace(1) @a, align 8
|
|
store <2 x i8> %1, ptr addrspace(1) @b, align 8
|
|
%2 = load <2 x i16>, ptr addrspace(1) @a, align 8
|
|
store <2 x i16> %2, ptr addrspace(1) @c, align 8
|
|
ret void
|
|
}
|