search for: lpmupdat

...oop`, and the `FunctionToLoopNestPassAdaptor` will construct the `LoopNest` object lazily for the given `LoopNestPass` to run on. The `LNPMUpdater` only support `revisitCurrentLoopNest()` and `markLoopNestAsDeleted()` since other functionalities like `addChildLoops()` and `addSiblingLoops()` that `LPMUpdater` provide don't seem to be meaningful since we're dealing with outer-most `LoopNest`s. Still, an analogy of `addSiblingLoops()` can be implemented as something like `addAllLoopNests()`. What's your opinion on that? Currently, `LoopNestToLoopPassAdaptor` is also implemented to allow in...

Hi, Thanks for your help! I've checked the sources that you mentioned. Currently, I think that I would need to implement a FunctionToLoopNestPassAdaptor which is essentially the same as the FunctionToLoopPassAdaptor but operates only on LI.getTopLevelLoops(). We might also need a LNPMUpdater (LoopNestPassManagerUpdater) which disallows adding inner-loops back into the pipeline, and