[SCEV] Fix ScalarEvolution tests under NPM
Many tests use opt's -analyze feature, which does not translate well to
NPM and has better alternatives. The alternative here is to explicitly
add a pass that calls ScalarEvolution::print().
The legacy pass manager RUNs aren't changing, but they are now pinned to
the legacy pass manager. For each legacy pass manager RUN, I added a
corresponding NPM RUN using the 'print<scalar-evolution>' pass. For
compatibility with update_analyze_test_checks.py and existing test
CHECKs, 'print<scalar-evolution>' now prints what -analyze prints per
function.
This was generated by the following Python script and failures were
manually fixed up:
import sys
for i in sys.argv:
with open(i, 'r') as f:
s = f.read()
with open(i, 'w') as f:
for l in s.splitlines():
if "RUN:" in l and ' -analyze ' in l and '\\' not in l:
f.write(l.replace(' -analyze ', ' -analyze -enable-new-pm=0 '))
f.write('\n')
f.write(l.replace(' -analyze ', ' -disable-output ').replace(' -scalar-evolution ', ' "-passes=print<scalar-evolution>" ').replace(" | ", " 2>&1 | "))
f.write('\n')
else:
f.write(l)
There are a couple failures still in ScalarEvolution under NPM, but
those are due to other unrelated naming conflicts.
Reviewed By: asbirlea
Differential Revision: https://reviews.llvm.org/D83798
2020-07-17 02:09:47 +08:00
|
|
|
; RUN: opt < %s "-passes=print<scalar-evolution>" -disable-output 2>&1 | FileCheck %s
|
2008-02-12 23:09:36 +08:00
|
|
|
; PR2002
|
|
|
|
|
|
2011-11-29 10:05:23 +08:00
|
|
|
; CHECK: Loop %loop: backedge-taken count is (100 + (-100 smax %n))
|
2008-02-12 23:09:36 +08:00
|
|
|
define void @foo(i8 %n) {
|
|
|
|
|
entry:
|
|
|
|
|
br label %loop
|
|
|
|
|
loop:
|
|
|
|
|
%i = phi i8 [ -100, %entry ], [ %i.inc, %next ]
|
|
|
|
|
%cond = icmp slt i8 %i, %n
|
|
|
|
|
br i1 %cond, label %next, label %return
|
|
|
|
|
next:
|
|
|
|
|
%i.inc = add i8 %i, 1
|
|
|
|
|
br label %loop
|
|
|
|
|
return:
|
|
|
|
|
ret void
|
|
|
|
|
}
|