Displaying 4 results from an estimated 4 matches for "calleeinfo".
2016 Sep 02
4
[ThinLTO] Importing based on PGO data
...sue 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 ProfileCount anywhere else.
The other thing I would like to mention is that I think we should start
using the summary v...
2016 Sep 02
4
[ThinLTO] Importing based on PGO data
...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 count in the callgraph summary?
> I think what is missing is the Profile SUmmary data itself -- that one
> should be copied over to thinLTO summary so t...
2016 Sep 02
2
[ThinLTO] Importing based on PGO data
...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 count in the callgraph summary?
>> I think what is missing is the Profile SUmmary data itself -- that one
>> should be copied over...
2016 Sep 02
3
[ThinLTO] Importing based on PGO data
...est 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 count in the callgraph summary?
> >> I think what is missing is the Profile SUmmary data itself -- that one...