Displaying 2 results from an estimated 2 matches for "verifyloopanalyses".
2016 Oct 19
2
LCSSA verification for the top-level loops
...els a bit wrong.
Originally I didn’t like this idea, but the more I think about it the more I like it. Currently all loop passes use (or should use) getLoopAnalysisUsage to record their pass requirements, so all of them should operate on the same set of analyses. What we can do is to add a function verifyLoopAnalyses to LPM and make it call verifiers for all these analyses.
So, instead of
if (getAnalaysisIfAvaliable<LCSSAVerifier>()) { CurrentLoop->verifyLCSSA(); )
we will have
verifyLoopAnalyses(CurrentLoop);
which will do:
CurrentLoop->verifyLCSSA();
CurrentLoop->verifyLoopSimplify(); //...
2016 Oct 17
2
LCSSA verification for the top-level loops
> On Oct 14, 2016, at 9:54 AM, Igor Laevsky <igor at azulsystems.com> wrote:
>>
>> Hi Michael,
> Hi Igor,
Hi Michael,
>
>>
>> +CC llvm-dev
>>
>> My guess is that it would be rather error prone to pinpoint exact places where we start populating new LPPassManager since it’s created lazily via LoopPass::assignPassManager. So we are risking to