Duncan Sands wrote: > It is easy to construct testcases for which this works, but sadly I was > unable to get > the optimization to occur even once in a trampoline heavy real-world program > without > jacking-up the inlining limit hugely (to 100000; 10000 wasn't enough). > Still, I'm > hoping that it may sometimes be useful.
Why does changing the inliner threshold help? Are you talking about inlining the trampoline itself or the llvm.init.trampoline intrinsic? Could we adjust the weights in the inliner so that it does it more often, seeing as a trampoline call is much more expensive than a regular call? Would you mind sending a small before and after example for the transformation implemented by your instcombine patch? Nick Lewycky _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
