search for: getnumbackedg

...Utils/UnrollLoop.cpp or something similar, but I'm not sure that's very pretty. Any suggestions? Additionally, after loop unrolling, the following check is made: // Update the loop information for this loop. // If we completely unrolled the loop, remove it from the parent. if (L->getNumBackEdges() == 0) LPM.deleteLoopFromQueue(L); This check probably needs to happen in every unroll pass that use loopUnroll. We could move this check into the loopUnroll function, but that requires passing in the LoopPassManager (LPM) to loopUnroll as well. Is that wanted? Overall, I've really onl...

I can get the loop header block by using getAnalysis < LoopInfo > ( *F ).isLoopHeader( BB ) But is there any way with with you can also check the blocks containing backedge. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130220/198e4421/attachment.html>

Hello Matthijs, Separating mechanism from policy is a good thing for the LoopUnroll pass. Instead of moving the policy to a subclass though, I think it'd be better to move the mechanism, the unrollLoop function, out to be a standalone utility function, with the LoopInfo object passed in explicitly. FoldBlockIntoPredecessor would also be good to make into a standalone utility function, since

...unrolled that it's still isLCSSAForm would be a good addition in any case. > > > Additionally, after loop unrolling, the following check is made: > // Update the loop information for this loop. > // If we completely unrolled the loop, remove it from the parent. > if (L->getNumBackEdges() == 0) > LPM.deleteLoopFromQueue(L); > > This check probably needs to happen in every unroll pass that use > loopUnroll. > We could move this check into the loopUnroll function, but that > requires > passing in the LoopPassManager (LPM) to loopUnroll as well. Is that...