Displaying 2 results from an estimated 2 matches for "504e6619".
Did you mean:
504e649
2010 Nov 30
0
[LLVMdev] LLVM Inliner
On Nov 30, 2010, at 2:19 PM, Xinliang David Li wrote:
> I understand that, but that implies that you have some model for code locality. Setting a global code growth limit is (in my opinion) a hack unless you are aiming for the whole program to fit in the icache (which I don't think anyone tries to do :).
>
> Yes, global growth limit may be good for size control, but is a hack for
2010 Nov 30
3
[LLVMdev] LLVM Inliner
On Mon, Nov 29, 2010 at 10:56 AM, Chris Lattner <clattner at apple.com> wrote:
> On Nov 28, 2010, at 11:39 PM, Xinliang David Li wrote:
>
> 1. Run the inliner on bar (noop, since it has no call sites)
>> 2. Run the per-function passes on bar. This generally shrinks it, and
>> prevents "abstraction penalty" from making bar look too big to inline.
>> 3.