search for: d4e63640

Star Tan wrote: > I have not yet found out why Polly produces such wrong code. IMO this is because Polly does not recognize a given number of patterns that occur after the scalar opts have transformed the code. There are a given number of assumptions that we took for granted and these do not hold down the pipeline. > However, maybe I should also investigate other points where we can move

Hi Tobias, At 2013-09-19 22:59:25,"Tobias Grosser" <tobias at grosser.es> wrote: >On 09/19/2013 04:46 PM, Star Tan wrote: >> Hi Tobias, >> >> >> I am trying to move Polly later. >> >> >> LLVM provides some predefined ExtensionPointTy: >> EP_EarlyAsPossible, >> EP_ModuleOptimizerEarly, >>