Displaying 5 results from an estimated 5 matches for "printmodulepasswrapper".
2018 Apr 20
2
LLVM Pass Managers
...> we'll soon have a *debugify-each* option, should we refactor the code to
> have a *apply-after-each=pass-name* option that automatically inserts
> *pass-name *to the pipeline after each optimization pass? We can even
> replace *print-after-all* option with
> *apply-after-each=PrintModulePassWrapper *for example?
>
>
> Speaking for myself, I'd rather type "opt -foo-each" over "opt
> -apply-after-each=foo".
>
I agree that "opt -foo-each" would be easier and more intuitive, but if
someone ever wants to apply foo after each pass, she will have to...
2018 Apr 20
0
LLVM Pass Managers
...(not only user-provided ones), and we'll soon have a debugify-each option, should we refactor the code to have a apply-after-each=pass-name option that automatically inserts pass-name to the pipeline after each optimization pass? We can even replace print-after-all option with apply-after-each=PrintModulePassWrapper for example?
Speaking for myself, I'd rather type "opt -foo-each" over "opt -apply-after-each=foo".
best,
vedant
>
> Son Tuan Vu
>
> On Thu, Apr 19, 2018 at 6:14 PM, Philip Pfaffe <philip.pfaffe at gmail.com <mailto:philip.pfaffe at gmail.com>>...
2018 Apr 20
0
LLVM Pass Managers
...(not only user-provided ones), and we'll soon have a debugify-each option, should we refactor the code to have a apply-after-each=pass-name option that automatically inserts pass-name to the pipeline after each optimization pass? We can even replace print-after-all option with apply-after-each=PrintModulePassWrapper for example?
>
> Speaking for myself, I'd rather type "opt -foo-each" over "opt -apply-after-each=foo".
>
> I agree that "opt -foo-each" would be easier and more intuitive, but if someone ever wants to apply foo after each pass, she will have to hack...
2018 Apr 20
2
LLVM Pass Managers
+ Vedant: what do you think about the last point, since Debugify is also
related?
Son Tuan Vu
On Thu, Apr 19, 2018 at 6:14 PM, Philip Pfaffe <philip.pfaffe at gmail.com>
wrote:
> Hi Son,
>
> PassManagerBuilder is used to populate legacy PassManagers. That role is
> taken over by PassBuilder for new-PM passes.
>
> Cheers,
> Philip
>
> 2018-04-18 13:40 GMT+02:00
2018 Apr 17
2
LLVM Pass Managers
...user-provided ones), and
we'll soon have a *debugify-each* option, should we refactor the code to
have a *apply-after-each=pass-name* option that automatically inserts
*pass-name
*to the pipeline after each optimization pass? We can even replace
*print-after-all* option with *apply-after-each=PrintModulePassWrapper *for
example?
Thank you all,
Son Tuan Vu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180417/9be9daca/attachment.html>