Displaying 1 result from an estimated 1 matches for "dd525b55".
2015 Apr 03
3
[LLVMdev] why are volatile memory accesses ordered?
Marking volatile accesses as !unordered seems excessively
conservative. For instance, LLVM is not able to optimize
declare void @escape(i32*)
declare i32 @read_only(i32) readonly
define i32 @f(i1* %c) {
entry:
%a = alloca i32
%b = alloca i32
call void @escape(i32* %a)
call void @escape(i32* %b)
%a0 = load i32, i32* %b, align 4
%lv = load volatile i32, i32* %b
%a1 = load i32,