[PATCH] D13443: Rework the LTO Pipeline, aligning closer to the O2/O3 pipeline.

[Teresa Johnson via llvm-commits]

On Mon, Oct 5, 2015 at 12:28 PM, Mehdi AMINI <mehdi.amini at apple.com> wrote:
> joker.eph added a comment.
>
> I'm not sure why inlining should be able to end up with smaller files, except in the case where an "internal linkage" function can end up with no call site. Do you see any other cases?

That's one of the cases I had in mind. The other is when inlining some
of the callsites can result in some nice clean up optimizations in the
caller (which is related to the comment about running the other
optimization passes that are currently after this early return).

>
> The inliner may take different decisions with more of the call graph available. Assuming the inliner heuristics are well tuned, running on a partial call-graph shouldn't result in better results but on the opposite only limits the freedom of it during LTO.
>
> If your only concern is about compile time, it is fairly easy to test and I can launch a run of our compile-time test-suite.
>
>
> http://reviews.llvm.org/D13443
>
>
>



-- 
Teresa Johnson | Software Engineer | tejohnson at google.com | 408-460-2413