Use the new PM syntax when specifying the pipeline in regression tests previously running "opt -newgvn ..." Instead we now do "opt -passes=newgvn ..." Notice that this also changes the aa-pipeline to become the default aa-pipeline instead of just basic-aa. Since these tests haven't been explicitly requesting basic-aa in the past (compared to the test cases updated in a separate patch involving "-basic-aa -newgvn") it is assumed that the exact aa-pipeline isn't important for the validity of the test cases. An alternative could have been to add -aa-pipeline=basic-aa as well to the run lines, but that might just add clutter in case the test cases do not care about the aa-pipeline. This is another step to move away from the legacy PM syntax when specifying passes in opt. Differential Revision: https://reviews.llvm.org/D118341
31 lines
850 B
LLVM
31 lines
850 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
|
|
; RUN: opt -passes=newgvn -S %s | FileCheck %s
|
|
; Ensure we do not incorrect do phi of ops
|
|
@d = external local_unnamed_addr global i32, align 4
|
|
|
|
define void @patatino() {
|
|
; CHECK-LABEL: @patatino(
|
|
; CHECK-NEXT: entry:
|
|
; CHECK-NEXT: [[TMP0:%.*]] = load i32, i32* @d, align 4
|
|
; CHECK-NEXT: br label [[FOR_END10:%.*]]
|
|
; CHECK: for.end10:
|
|
; CHECK-NEXT: [[OR:%.*]] = or i32 [[TMP0]], 8
|
|
; CHECK-NEXT: br i1 undef, label [[IF_END:%.*]], label [[FOR_END10]]
|
|
; CHECK: if.end:
|
|
; CHECK-NEXT: ret void
|
|
;
|
|
entry:
|
|
%0 = load i32, i32* @d, align 4
|
|
br label %for.end10
|
|
|
|
for.end10:
|
|
%f.0 = phi i32 [ undef, %entry ], [ 8, %for.end10 ]
|
|
%or = or i32 %0, %f.0
|
|
%mul12 = mul nsw i32 %or, undef
|
|
br i1 undef, label %if.end, label %for.end10
|
|
|
|
if.end:
|
|
ret void
|
|
}
|
|
|