Displaying 3 results from an estimated 3 matches for "pgso".
Did you mean:
gso
2020 Sep 10
2
[RFC] New Feature Proposal: De-Optimizing Cold Functions using PGO Info
FYI David is referring to PGSO (profile-guided size optimization) as it exists directly under that name, see: https://reviews.llvm.org/D67120. And yeah using PGSO is selecting optsize while this change is selecting optnone.
On 9/9/20, 10:58 AM, "llvm-dev on behalf of Tobias Hieta via llvm-dev" <llvm-dev-bounces at...
2020 Sep 10
2
[RFC] New Feature Proposal: De-Optimizing Cold Functions using PGO Info
On Wed, Sep 9, 2020 at 9:23 PM Wenlei He via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I think calling PGSO size opt is probably a bit misleading though. It’s
> more of an adaptive opt strategy, and it can improve performance too due to
> better locality. We have something similar internally for selecting opt
> level based on profile hotness too under AutoFDO.
>
>
>
> Perhaps similar...
2020 Sep 09
2
[RFC] New Feature Proposal: De-Optimizing Cold Functions using PGO Info
On Wed, 9 Sep 2020 at 18:15, Min-Yih Hsu via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> David mentioned in D87337 that LLVM has used similar techniques on code
> size (not sure what he was referencing, my guess will be something related
> to hot-cold code splitting).
>
IIUC, it's just using optsize instead of optnone. The idea is that, if the
code really doesn't