Displaying 3 results from an estimated 3 matches for "b1e3af1a".
2018 Mar 15
0
Commit module to Git after each Pass
Hmm...
I tried Alexandre's fix from D44244 and surprisingly it appears that
just using -print-module-scope w/o
any additional git actions is waaaay slower on my testcase than
-git-commit-module-all.
Hell, even a plan -print-after-all is slower:
] time R/bin/opt -O3 some-ir.ll -disable-output -git-commit-after-all
2>/dev/null
real 0m8.041s
user 0m7.133s
sys 0m0.936s
] time
2018 Mar 15
2
Commit module to Git after each Pass
..._____________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180315/b1e3af1a/attachment.html>
2018 Mar 15
2
Commit module to Git after each Pass
On 03/15/2018 01:32 PM, Fedor Sergeev via llvm-dev wrote:
> For this to be really usable in this setup we need additionally to:
> - extend -print-module-scope to cover basic block passes
> - introduce a clear way to separate module IRs as those are being
> printed by -print-after-all
>
> But yes, it should work, and a wrapper that pipes to git fast-import
> seems to be