This creates the new-style LoopPassManager and wires it up with dummy
and print passes.
TODO:
- Is a BasicBlock name sufficient for Loop::getName(), or should we include the containing function's name as well?
- LoopAnalysisManagerFunctionProxy::run could use an assert to ensure that we don't run Loop Analyses before the proxy is created, but this can't work without a good model for invalidating the cache between functions. Note: this is an existing issue with FunctionAMModuleProxy as well.
- There is no LoopVerifierPass. This can be added later.
I think this is fine, the caller can dig out more info as needed.