[llvm-dev] [RFC] Enable Partial Inliner by default

[Evgeny Astigeevich via llvm-dev]

Hi Sean,

Thank you for reminding me.
It looks like it get lost among tons of emails and other tasks.
I’ll check if the code size issues still exist.

Thanks,
Evgeny Astigeevich

From: Sean Fertile <sd.fertile at gmail.com>
Date: Monday, 29 January 2018 at 19:52
To: Florian Hahn <Florian.Hahn at arm.com>
Cc: Evgeny Astigeevich <Evgeny.Astigeevich at arm.com>, Graham Yiu <gyiu at ca.ibm.com>, "junbuml at codeaurora.org" <junbuml at codeaurora.org>, "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org>, Tobias Grosser <tobias.grosser at inf.ethz.ch>, nd <nd at arm.com>
Subject: Re: [llvm-dev] [RFC] Enable Partial Inliner by default


Hello All,

This conversations seems to have fizzled out and I would like to try to revive it. My intention is to pick up where Graham left off with enabling partial-inlining by default.

On Sat, Dec 9, 2017 at 7:47 AM, Florian Hahn via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Hi,

On 13/11/2017 14:47, Evgeny Astigeevich via llvm-dev wrote:
Hi Graham,

I created a bug report with a reproducer for the failures I’ve got: https://bugs.llvm.org/show_bug.cgi?id=35288

That bug should be fixed by https://reviews.llvm.org/rL320199

Cheers,
Florian

Thanks for fixing this Florian. Now that this is no longer blocking, are there other concerns over enabling PI by default?

Evgeny, did you get a chance to look into the code-size regressions on AArch targets? What do you think about moving ahead with this?

Thanks
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180129/513c68bf/attachment.html>