[LSR] Auto-generate check lines for test.

Checking the full output provides more context and makes it easier to
review changes to the test in a follow-up patch.

1 files changed, 22 insertions, 5 deletions

diff --git a/llvm/test/Transforms/LoopStrengthReduce/X86/2011-11-29-postincphi.ll b/llvm/test/Transforms/LoopStrengthReduce/X86/2011-11-29-postincphi.ll
index 8053940df13f..841836c7d2dd 100644
--- a/llvm/test/Transforms/LoopStrengthReduce/X86/2011-11-29-postincphi.ll
+++ b/llvm/test/Transforms/LoopStrengthReduce/X86/2011-11-29-postincphi.ll
@@ -1,3 +1,4 @@
+; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
 ; RUN: llc < %s | FileCheck %s
 ;
 ; PR11431: handle a phi operand that is replaced by a postinc user.
@@ -10,12 +11,28 @@ target triple = "x86_64-unknown-linux-gnu"
 declare i1 @check() nounwind
 
 ; Check that LSR did something close to the behavior at the time of the bug.
-; CHECK: @sqlite3DropTriggerPtr
-; CHECK: incq %r{{[a-d]}}x
-; CHECK: jne
-; CHECK: decq %r{{[a-d]}}x
-; CHECK: ret
 define i64 @sqlite3DropTriggerPtr() nounwind {
+; CHECK-LABEL: sqlite3DropTriggerPtr:
+; CHECK:       # %bb.0: # %bb
+; CHECK-NEXT:    pushq %rbx
+; CHECK-NEXT:    movl $1, %ebx
+; CHECK-NEXT:    callq check@PLT
+; CHECK-NEXT:    .p2align 4, 0x90
+; CHECK-NEXT:  .LBB0_1: # %bb1
+; CHECK-NEXT:    # =>This Inner Loop Header: Depth=1
+; CHECK-NEXT:    testb %al, %al
+; CHECK-NEXT:    je .LBB0_4
+; CHECK-NEXT:  # %bb.2: # %bb4
+; CHECK-NEXT:    # in Loop: Header=BB0_1 Depth=1
+; CHECK-NEXT:    incq %rbx
+; CHECK-NEXT:    testb %al, %al
+; CHECK-NEXT:    jne .LBB0_1
+; CHECK-NEXT:  # %bb.3: # %bb8split
+; CHECK-NEXT:    decq %rbx
+; CHECK-NEXT:  .LBB0_4: # %bb8
+; CHECK-NEXT:    movq %rbx, %rax
+; CHECK-NEXT:    popq %rbx
+; CHECK-NEXT:    retq
 bb:
   %cmp = call zeroext i1 @check()
   br label %bb1