Displaying 4 results from an estimated 4 matches for "ishotcount".
2016 Sep 02
4
[ThinLTO] Importing based on PGO data
Hi,
I am working right now on importing based on PGO/FDO data. There is one
issue that I found - when we calculate the list of imports, we can't get
the ProfileSummaryInfo, which is the best and I
think only valid way of checking if callsite/callee is hot (isHotCount()).
There are 2 solutions that I come up with Teresa and Easwaran:
1. Add PGO data to summary
2. Replace CalleeInfo::ProfileCount with enum {None, Cold, Hot} computed
during computing summary.
I like the 2. much more. It will reduce the summary size slightly and I
don't think we will need Pro...
2016 Sep 02
4
[ThinLTO] Importing based on PGO data
...t; I am working right now on importing based on PGO/FDO data. There is one
> > issue that I found - when we calculate the list of imports, we can't get
> the
> > ProfileSummaryInfo, which is the best and I
> > think only valid way of checking if callsite/callee is hot
> (isHotCount()).
> > There are 2 solutions that I come up with Teresa and Easwaran:
> >
> > 1. Add PGO data to summary
> > 2. Replace CalleeInfo::ProfileCount with enum {None, Cold, Hot} computed
> > during computing summary.
>
>
> Don't we already have edge profile co...
2016 Sep 02
3
[ThinLTO] Importing based on PGO data
...re is
> one
> >> > issue that I found - when we calculate the list of imports, we can't
> get
> >> > the
> >> > ProfileSummaryInfo, which is the best and I
> >> > think only valid way of checking if callsite/callee is hot
> >> > (isHotCount()).
> >> > There are 2 solutions that I come up with Teresa and Easwaran:
> >> >
> >> > 1. Add PGO data to summary
> >> > 2. Replace CalleeInfo::ProfileCount with enum {None, Cold, Hot}
> computed
> >> > during computing summary.
> &...
2016 Sep 02
2
[ThinLTO] Importing based on PGO data
...t now on importing based on PGO/FDO data. There is one
>> > issue that I found - when we calculate the list of imports, we can't
>> get the
>> > ProfileSummaryInfo, which is the best and I
>> > think only valid way of checking if callsite/callee is hot
>> (isHotCount()).
>> > There are 2 solutions that I come up with Teresa and Easwaran:
>> >
>> > 1. Add PGO data to summary
>> > 2. Replace CalleeInfo::ProfileCount with enum {None, Cold, Hot} computed
>> > during computing summary.
>>
>>
>> Don't...