[PATCH] D13443: Rework the LTO Pipeline, aligning closer to the O2/O3 pipeline.
Mehdi AMINI via llvm-commits
llvm-commits at lists.llvm.org
Mon Oct 5 17:50:49 PDT 2015
joker.eph added a comment.
Right now my view of it is that if I get a performance improvement by running two times the inliner and the "peephole" passes, then it is a bug. If it is not a bug it means that the O3 pipeline is affected as well and we might run it two times there as well. Does it make sense?
I ran the LLVM benchmark suite + some internals with a return before and after the inliner+peephole phase. Stopping before the inliner during the compile phase ends up with 13 regressions and 20 improvements, compared to running the inliner during the compile phase. I sent you some more details by email.
http://reviews.llvm.org/D13443
More information about the llvm-commits
mailing list