mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-26 04:32:44 +01:00
09cfe7939a
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
23 lines
583 B
LLVM
23 lines
583 B
LLVM
; RUN: opt < %s -analyze -enable-new-pm=0 -scalar-evolution
|
|
; RUN: opt < %s -disable-output -scalar-evolution
|
|
; PR1827
|
|
|
|
declare void @use(i32)
|
|
|
|
define void @foo() {
|
|
entry:
|
|
br label %loop_1
|
|
|
|
loop_1: ; preds = %loop_1, %entry
|
|
%a = phi i32 [ 2, %entry ], [ %b, %loop_1 ] ; <i32> [#uses=2]
|
|
%c = phi i32 [ 5, %entry ], [ %d, %loop_1 ] ; <i32> [#uses=1]
|
|
%b = add i32 %a, 1 ; <i32> [#uses=1]
|
|
%d = add i32 %c, %a ; <i32> [#uses=3]
|
|
%A = icmp ult i32 %d, 50 ; <i1> [#uses=1]
|
|
br i1 %A, label %loop_1, label %endloop
|
|
|
|
endloop: ; preds = %loop_1
|
|
call void @use(i32 %d)
|
|
ret void
|
|
}
|