search for: ep_loopoptimizerbegin

...you have any further suggestion? Yes, fully correct. I would play with solution two. Why would you add Polly after the loop rotate pass? I would possibly add it at the beginning of the loop optimizer (right before the loop rotation pass) possibly experimenting with a new extension point called EP_LoopOptimizerBegin. Cheers, Tobias

Hi Tobias, I am trying to move Polly later. LLVM provides some predefined ExtensionPointTy: EP_EarlyAsPossible, EP_ModuleOptimizerEarly, EP_LoopOptimizerEnd, EP_ScalarOptimizerLate, ... Currently Polly uses "EP_EarlyAsPossible" to run as early as possible. As what you suggested: >Instead of removing canonicalization passes, I believe we may want to >move

...lly after the loop rotate pass? Forgot it. I just wanted to give an immature example to show how to move Polly to other points. >I would possibly add it at the beginning of the loop optimizer (right >before the loop rotation pass) possibly experimenting with a new >extension point called EP_LoopOptimizerBegin. > Thanks for your advice. I have tried to move Polly immediately before the loop rotation pass. The temporary patch file can be reached on http://llvm.org/bugs/attachment.cgi?id=11262. First of all, I evaluated Polly's canonicalization passes based on this patch file. Results are posted on...

...ion? > >Yes, fully correct. I would play with solution two. Why would you add  >Polly after the loop rotate pass? > >I would possibly add it at the beginning of the loop optimizer (right  >before the loop rotation pass) possibly experimenting with a new  >extension point called EP_LoopOptimizerBegin. > >Cheers, >Tobias > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130925/ed6c476d/attachment.html>