[cfe-dev] Passes after Polly | How are Passes sequenced without the PassRegistry ?

[Philip Pfaffe via cfe-dev]

The PassManagerBuilder that constructs the -O pipelines offers multiple
ExtensionPoints at which optimizer plugins can insert themselves into
optimizer pipelines.

Here's how plugins can do this:
http://llvm.org/doxygen/structllvm_1_1RegisterStandardPasses.html

In Polly, you can find the registration part a bit further down in the file
you linked:
https://github.com/llvm-mirror/polly/blob/master/lib/Support/RegisterPasses.cpp#L417

Cheers,
Philip

2017-05-12 14:20 GMT+02:00 SANJAY SRIVALLABH SINGAPURAM <
llvmresch_int01 at iith.ac.in>:

> Hello,
>
> I was trying to find out what passes are sequenced after Polly in clang. I
> need to know this since I'm seeing a difference between the files
> kernel-before.ll and kernel.ll generated by the command clang -g -O3
> -mllvm -polly -mllvm -polly-dump-before -S -emit-llvm, where
> kernel-before.ll is the file received by Polly.
>
> I assumed that the clang driver registers the Passes just like opt or
> Julia
> <https://github.com/JuliaLang/julia/blob/973d926584a39e48d173dc9ec62d2b8908a3c544/src/jitlayers.cpp#L197-L205>
> does by calling polly::registerPollyPasses ( in the
> <polly_src>/lib/Support/RegisterPasses.cpp
> <https://github.com/llvm-mirror/polly/blob/master/lib/Support/RegisterPasses.cpp> ).
> But, it was a surprise to not find a call to registerPollyPasses inside
> clang.
>
> Summarising,
>
>    - How is Polly called from Clang ?
>    - What are the Passes sequenced after Polly ?
>
> Thanks,
> Sanjay
>
> --
> You received this message because you are subscribed to the Google Groups
> "Polly Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to polly-dev+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20170512/d349aace/attachment.html>