ed9117f88d
Some atomic loads are implemented as cmpxchg (particularly if large or floating), and that usually requires write access to the memory involved or it will segfault. We can still propagate the constant value to users we understand though. llvm-svn: 360662
35 lines
684 B
LLVM
35 lines
684 B
LLVM
; RUN: opt -globalopt < %s -S -o - | FileCheck %s
|
|
|
|
@GV1 = internal global i64 1
|
|
@GV2 = internal global i32 0
|
|
|
|
; CHECK: @GV1 = internal unnamed_addr global i64 1
|
|
; CHECK: @GV2 = internal unnamed_addr global i32 0
|
|
|
|
define void @test1() {
|
|
entry:
|
|
%0 = load atomic i8, i8* bitcast (i64* @GV1 to i8*) acquire, align 8
|
|
ret void
|
|
}
|
|
|
|
; PR17163
|
|
define void @test2a() {
|
|
entry:
|
|
store atomic i32 10, i32* @GV2 seq_cst, align 4
|
|
ret void
|
|
}
|
|
define i32 @test2b() {
|
|
entry:
|
|
%atomic-load = load atomic i32, i32* @GV2 seq_cst, align 4
|
|
ret i32 %atomic-load
|
|
}
|
|
|
|
|
|
define i64 @test3() {
|
|
; CHECK-LABEL: @test3
|
|
; CHECK: ret i64 1
|
|
|
|
%val = load atomic i64, i64* @GV1 acquire, align 8
|
|
ret i64 %val
|
|
}
|