93421108d2
Having a NoOpLoopNestPass can ensure that only outermost loop is invoked for a LoopNestPass with a lit test. There are some existing passes that are implemented as LoopNestPass, but they are still using LOOP_PASS macro. It would be easier to identify LoopNestPasses with a LOOPNEST_PASS macro. Differential Revision: https://reviews.llvm.org/D113185
29 lines
884 B
LLVM
29 lines
884 B
LLVM
; RUN: opt --print-passes | FileCheck %s
|
|
|
|
; CHECK: Module passes:
|
|
; CHECK: no-op-module
|
|
; CHECK: Module analyses:
|
|
; CHECK: no-op-module
|
|
; CHECK: Module alias analyses:
|
|
; CHECK: globals-aa
|
|
; CHECK: CGSCC passes:
|
|
; CHECK: no-op-cgscc
|
|
; CHECK: CGSCC analyses:
|
|
; CHECK: no-op-cgscc
|
|
; CHECK: Function passes:
|
|
; CHECK: no-op-function
|
|
; CHECK: Function passes with params:
|
|
; CHECK: loop-unroll<O0;O1;O2;O3;full-unroll-max=N;no-partial;partial;no-peeling;peeling;no-profile-peeling;profile-peeling;no-runtime;runtime;no-upperbound;upperbound>
|
|
; CHECK: Function analyses:
|
|
; CHECK: no-op-function
|
|
; CHECK: Function alias analyses:
|
|
; CHECK: basic-aa
|
|
; CHECK: LoopNest passes:
|
|
; CHECK: no-op-loopnest
|
|
; CHECK: Loop passes:
|
|
; CHECK: no-op-loop
|
|
; CHECK: Loop passes with params:
|
|
; CHECK: simple-loop-unswitch<nontrivial;no-nontrivial;trivial;no-trivial>
|
|
; CHECK: Loop analyses:
|
|
; CHECK: no-op-loop
|