39 lines · plain
1; RUN: opt -passes='print<access-info>' -disable-output < %s 2>&1 | FileCheck %s2 3; Test that the loop accesses are proven safe in this case.4; The analyzer uses to be confused by the "diamond" because getUnderlyingObjects5; is saying that the two pointers can both points to null. The loop analyzer6; needs to ignore null in the results returned by getUnderlyingObjects.7 8; CHECK: Memory dependences are safe with run-time checks9 10 11; ModuleID = 'bugpoint-reduced-simplified.bc'12target datalayout = "e-m:o-i64:64-f80:128-n8:16:32:64-S128"13target triple = "x86_64-apple-macosx10.11.0"14 15; Function Attrs: ssp uwtable16define void @foo(i1 %cond, ptr %ptr1, ptr %ptr2) {17 br i1 %cond, label %.preheader, label %diamond18 19diamond: ; preds = %.noexc.i.i20 br label %.preheader21 22.preheader: ; preds = %diamond, %023 %ptr1_or_null = phi ptr [ null, %0 ], [ %ptr1, %diamond ]24 %ptr2_or_null = phi ptr [ null, %0 ], [ %ptr2, %diamond ]25 br label %.lr.ph26 27.lr.ph: ; preds = %.lr.ph, %.preheader28 %indvars.iv = phi i64 [ %indvars.iv.next, %.lr.ph ], [ 10, %.preheader ]29 %indvars.iv.next = add nsw i64 %indvars.iv, -130 %tmp4 = getelementptr inbounds i32, ptr %ptr2_or_null, i64 %indvars.iv.next31 %tmp5 = load i32, ptr %tmp4, align 432 %tmp6 = getelementptr inbounds i32, ptr %ptr1_or_null, i64 %indvars.iv.next33 store i32 undef, ptr %tmp6, align 434 br i1 false, label %.lr.ph, label %.end35 36.end:37 ret void38}39