[llvm-diff] Precommit: Add loop test case with forward reference

[jsilvanus]

Summary

Diffing phi nodes was recently added to llvm-diff (https://reviews.llvm.org/D114211).
However, there currently is a limitation where equivalent values
cannot be detected as such, leading to false positive diff reports.

If a phi node refers a value defined in a basic block dominated by
the current basic block, for example a phi node in a loop header referring
a value defined in the loop body, we cannot prove equivalence of the referred
values, because the basic block containing the variable definition has
not yet been processed.

This commit adds a test case showing this behavior, serving as a precommit
for an upcoming fix of the above.

[jsilvanus]

Fix branch target.

[dblaikie]

Sure, sounds OK - we don't usually precommit tests, but it can make diffs clearer when submitting - not sure about this one in particular, but I don't mind too much just a thought for next time.

[jsilvanus]

Thanks for reviewing.

Yes, the intention is to help reviewing the actual patch, I was asked in the past to precommit such tests.

llvm/test/tools/llvm-diff/loop.ll

+; Diff file with itself
+; Due to a current limitation in llvm-diff, a diff is reported here.
+; RUN: not llvm-diff %s %s 2>&1 | FileCheck --check-prefix=SAME-FILE %s
+
+; Replace %newvar1 with %newvar2 in the phi node. This can only
+; be detected to be different once BB1 has been processed.
+; RUN: rm -f %t.ll
+; RUN: cat %s | sed -e 's/ %newvar1, %BB1 / %newvar2, %BB1 /' > %t.ll
+; RUN: not llvm-diff %s %t.ll 2>&1 | FileCheck --check-prefix DIFFERENT-VAR %s
+
+; SAME-FILE:      in function func:
+; SAME-FILE-NEXT:   in block %BB0:
+; SAME-FILE-NEXT:     >   %var = phi i32 [ 0, %ENTRY ], [ %newvar1, %BB1 ]
+; SAME-FILE-NEXT:     >   %cnd = icmp eq i32 %var, 0
+; SAME-FILE-NEXT:     >   br i1 %cnd, label %BB1, label %END
+; SAME-FILE-NEXT:     <   %var = phi i32 [ 0, %ENTRY ], [ %newvar1, %BB1 ]
+; SAME-FILE-NEXT:     <   %cnd = icmp eq i32 %var, 0
+; SAME-FILE-NEXT:     <   br i1 %cnd, label %BB1, label %END
+
+; DIFFERENT-VAR:      in function func:
+; DIFFERENT-VAR-NEXT:   in block %BB0:
+; DIFFERENT-VAR-NEXT:     >   %var = phi i32 [ 0, %ENTRY ], [ %newvar2, %BB1 ]
+; DIFFERENT-VAR-NEXT:     >   %cnd = icmp eq i32 %var, 0
+; DIFFERENT-VAR-NEXT:     >   br i1 %cnd, label %BB1, label %END
+; DIFFERENT-VAR-NEXT:     <   %var = phi i32 [ 0, %ENTRY ], [ %newvar1, %BB1 ]
+; DIFFERENT-VAR-NEXT:     <   %cnd = icmp eq i32 %var, 0
+; DIFFERENT-VAR-NEXT:     <   br i1 %cnd, label %BB1, label %END
+define i32 @func() {
+ENTRY:
+  br label %BB0
+
+BB0:
+  ; When diffing this phi node, we need to detect whether
+  ; %newvar1 is equivalent, which is not known until BB1 has been processed.
+  %var = phi i32 [ 0, %ENTRY ], [ %newvar1, %BB1 ]
+  %cnd = icmp eq i32 %var, 0
+  br i1 %cnd, label %BB1, label %END
+
+BB1:
+  %newvar1 = add i32 %var, 1
+  %newvar2 = add i32 %var, 2
+  br label %BB1
+
+END:
+  ; Equivalence of the ret depends on equivalence of %var.
+  ; Even if %var differs, we do not report a diff here, because
+  ; this is an indirect diff caused by another diff.
+  ret i32 %var
+}