Displaying 15 results from an estimated 15 matches for "getpgofuncname".
2016 May 25
3
The state of IRPGO (3 remaining work items)
...;>
>>
>> - Warnings
>>
>> We identified 3 classes of issues which manifest as spammy warnings when
>> applying profile data with IRPGO (these affect FEPGO also I believe, but we
>> looked in depth at IRPGO):
>>
>> 1. The main concerning one is that getPGOFuncName mangles the filename
>> into the counter name. This causes us to get
>> instrprof_error::unknown_function when the pgo-use build is done in a
>> different build directory from the training build (which is a reasonable
>> thing to support). In this situation, PGO data is usel...
2016 May 25
0
The state of IRPGO (3 remaining work items)
...workloads (which is most code).
>
>
> - Warnings
>
> We identified 3 classes of issues which manifest as spammy warnings when
> applying profile data with IRPGO (these affect FEPGO also I believe, but we
> looked in depth at IRPGO):
>
> 1. The main concerning one is that getPGOFuncName mangles the filename
> into the counter name. This causes us to get
> instrprof_error::unknown_function when the pgo-use build is done in a
> different build directory from the training build (which is a reasonable
> thing to support). In this situation, PGO data is useless for all `sta...
2016 May 25
0
The state of IRPGO (3 remaining work items)
...- Warnings
>>>
>>> We identified 3 classes of issues which manifest as spammy warnings when
>>> applying profile data with IRPGO (these affect FEPGO also I believe, but we
>>> looked in depth at IRPGO):
>>>
>>> 1. The main concerning one is that getPGOFuncName mangles the filename
>>> into the counter name. This causes us to get
>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>> different build directory from the training build (which is a reasonable
>>> thing to support). In this situation,...
2016 May 24
5
The state of IRPGO (3 remaining work items)
...s, which might be beneficial for non-game
workloads (which is most code).
- Warnings
We identified 3 classes of issues which manifest as spammy warnings when
applying profile data with IRPGO (these affect FEPGO also I believe, but we
looked in depth at IRPGO):
1. The main concerning one is that getPGOFuncName mangles the filename into
the counter name. This causes us to get instrprof_error::unknown_function
when the pgo-use build is done in a different build directory from the
training build (which is a reasonable thing to support). In this situation,
PGO data is useless for all `static` functions (and...
2016 May 24
0
The state of IRPGO (3 remaining work items)
...rmance data before submitting the patch.
> - Warnings
>
> We identified 3 classes of issues which manifest as spammy warnings when
> applying profile data with IRPGO (these affect FEPGO also I believe, but we
> looked in depth at IRPGO):
>
> 1. The main concerning one is that getPGOFuncName mangles the filename
> into the counter name. This causes us to get
> instrprof_error::unknown_function when the pgo-use build is done in a
> different build directory from the training build (which is a reasonable
> thing to support). In this situation, PGO data is useless for all `sta...
2016 May 25
0
The state of IRPGO (3 remaining work items)
...patch.
> >
> > - Warnings
> >
> > We identified 3 classes of issues which manifest as spammy warnings when
> applying profile data with IRPGO (these affect FEPGO also I believe, but we
> looked in depth at IRPGO):
> >
> > 1. The main concerning one is that getPGOFuncName mangles the filename
> into the counter name. This causes us to get
> instrprof_error::unknown_function when the pgo-use build is done in a
> different build directory from the training build (which is a reasonable
> thing to support). In this situation, PGO data is useless for all `sta...
2016 Jun 03
2
The state of IRPGO (3 remaining work items)
...>>>> >
>>>> > We identified 3 classes of issues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>>>> >
>>>> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and...
2016 May 24
6
The state of IRPGO (3 remaining work items)
...rformance data before submitting the patch.
>
> - Warnings
>
> We identified 3 classes of issues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>
> 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and...
2016 May 25
2
The state of IRPGO (3 remaining work items)
...gt; - Warnings
>> >
>> > We identified 3 classes of issues which manifest as spammy warnings
>> when applying profile data with IRPGO (these affect FEPGO also I believe,
>> but we looked in depth at IRPGO):
>> >
>> > 1. The main concerning one is that getPGOFuncName mangles the filename
>> into the counter name. This causes us to get
>> instrprof_error::unknown_function when the pgo-use build is done in a
>> different build directory from the training build (which is a reasonable
>> thing to support). In this situation, PGO data is usel...
2016 Jun 01
4
The state of IRPGO (3 remaining work items)
...itting the patch.
> >
> > - Warnings
> >
> > We identified 3 classes of issues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
> >
> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and...
2016 Jun 02
2
The state of IRPGO (3 remaining work items)
...t; >
>> > - Warnings
>> >
>> > We identified 3 classes of issues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>> >
>> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and...
2016 Jun 02
4
The state of IRPGO (3 remaining work items)
...> - Warnings
>>> >
>>> > We identified 3 classes of issues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>>> >
>>> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and...
2016 Jun 03
5
The state of IRPGO (3 remaining work items)
...entified 3 classes of issues which manifest as spammy warnings
>>>>> when applying profile data with IRPGO (these affect FEPGO also I believe,
>>>>> but we looked in depth at IRPGO):
>>>>> >
>>>>> > 1. The main concerning one is that getPGOFuncName mangles the
>>>>> filename into the counter name. This causes us to get
>>>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>>>> different build directory from the training build (which is a reasonable
>>>>> thing...
2016 Jun 13
2
The state of IRPGO (3 remaining work items)
...ch manifest as spammy
>>>>>>> warnings when applying profile data with IRPGO (these affect FEPGO also I
>>>>>>> believe, but we looked in depth at IRPGO):
>>>>>>> >
>>>>>>> > 1. The main concerning one is that getPGOFuncName mangles the
>>>>>>> filename into the counter name. This causes us to get
>>>>>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>>>>>> different build directory from the training build (which is a reasonable
>...
2016 Jun 23
0
The state of IRPGO (3 remaining work items)
...es of issues which manifest as spammy warnings
>>>>>> when applying profile data with IRPGO (these affect FEPGO also I believe,
>>>>>> but we looked in depth at IRPGO):
>>>>>> >
>>>>>> > 1. The main concerning one is that getPGOFuncName mangles the
>>>>>> filename into the counter name. This causes us to get
>>>>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>>>>> different build directory from the training build (which is a reasonable
>>>>...