search for: urol

...nique compared to func/module passes in that they could destroy the loop they worked on. And there might be no loop to print after that (btw, there is a known bug in new pass manager where it tries to print deleted loop in this situation - nothing good happens!). In your case loop unroll can fully uroll the loop, essentially removing the Loop. If you have suggestions on how to improve behavior in such cases I would be happy to discuss this further. regards, Fedor 8 нояб. 2018 г. 12:38 пользователь "Markus Lavin via llvm-dev" <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists....

Hi, I recently worked on an issue where I realized that -print-after-all does not cover all passes run by the pass manager. E.g. it seems that loop passes are not fully covered and I could find that loop transformations showed up in the dump of the next non-loop pass (which happened to be 'Combine redundant instructions' and that was rather confusing). Specifying both -print-before-all

On 27.02.2012, at 18:49, Eli Friedman wrote: > On Mon, Feb 27, 2012 at 9:30 AM, Benjamin Kramer > <benny.kra at googlemail.com> wrote: >> >> On 27.02.2012, at 17:13, Николай Лихогруд wrote: >> >>> Dear LLVM, >>> >>> Consider two loops with one interation - >>> First with constant lower bound, second with usual

On Mon, Feb 27, 2012 at 9:30 AM, Benjamin Kramer <benny.kra at googlemail.com> wrote: > > On 27.02.2012, at 17:13, Николай Лихогруд wrote: > >> Dear LLVM, >> >>     Consider two loops with one interation - >>     First with constant lower bound, second with usual non-constant lower bound: >> >>     int main(int argc, char ** argv) >>     {