Displaying 3 results from an estimated 3 matches for "canonicalizeir".
Did you mean:
canonicalize
2016 Jul 26
2
[PM] I think that the new PM needs to learn about inter-analysis dependencies...
...>> >
>> > ```
>> > FooTransformation.cpp:
>> >
>> > PreservedAnalyses FooTransformation::run(Function &F, AnalysisManager
>> AM) {
>> > // Must be called before getting analyses, as it might invalidate
>> some.
>> > canonicalizeIR<LCSSA>(F, AM);
>> >
>> > ...
>> > }
>> >
>> >
>> > include/IR/Canonicalization.h:
>> >
>> > template <typename CanonicalizationT, typename IRUnitT>
>> > void canonicalizeIR(IRUnitT &IR, AnalysisManage...
2016 Jul 25
3
[PM] I think that the new PM needs to learn about inter-analysis dependencies...
...not this transformation has been performed.
>
> ```
> FooTransformation.cpp<http://FooTransformation.cpp>:
>
> PreservedAnalyses FooTransformation::run(Function &F, AnalysisManager AM) {
> // Must be called before getting analyses, as it might invalidate some.
> canonicalizeIR<LCSSA>(F, AM);
>
> ...
> }
>
>
> include/IR/Canonicalization.h:
>
> template <typename CanonicalizationT, typename IRUnitT>
> void canonicalizeIR(IRUnitT &IR, AnalysisManager &AM) {
> using IndicatorT = typename CanonicalizationT::IndicatorAnaly...
2016 Jul 22
4
[PM] I think that the new PM needs to learn about inter-analysis dependencies...
The more closely I look at this, the more it seems like there may be a
useful incremental step in the transition to the new PM: use the new PM
analysis machinery in the old PM. If this is possible, it will simplify the
old PM and (hopefully) allow an incremental transition to the new PM
instead of a flag day transition for the switch.
I.e., AFAICT, the new PM transition is essentially about 2