search for: instrprof_error

Displaying 15 results from an estimated 15 matches for "instrprof_error".

The state of IRPGO (3 remaining work items)
2016 May 24
5
The state of IRPGO (3 remaining work items)
...nings 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 as a byproduct results in a huge volume of warnings). 2. In different TU's, p...
The state of IRPGO (3 remaining work items)
2016 May 25
3
The state of IRPGO (3 remaining work items)
...st 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 as a byproduct results in a huge volume of warnings). &...
The state of IRPGO (3 remaining work items)
2016 May 25
0
The state of IRPGO (3 remaining work items)
...s 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 as a byproduct results in a huge volume of warnings). > Rong,...
The state of IRPGO (3 remaining work items)
2016 May 25
0
The state of IRPGO (3 remaining work items)
...en >>> 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 as a byproduct results in a huge volume of...
The state of IRPGO (3 remaining work items)
2016 May 24
0
The state of IRPGO (3 remaining work items)
...s 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 as a byproduct results in a huge volume of warnings). > This ca...
The state of IRPGO (3 remaining work items)
2016 May 25
0
The state of IRPGO (3 remaining work items)
...s 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 as a byproduct results in a huge volume of warnings). > > &gt...
The state of IRPGO (3 remaining work items)
2016 Jun 03
2
The state of IRPGO (3 remaining work items)
...ich 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 as a byproduct results in a huge volume of warnings). >>>> > >&g...
The state of IRPGO (3 remaining work items)
2016 May 24
6
The state of IRPGO (3 remaining work items)
...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 as a byproduct results in a huge volume of warnings). > > This can be enhan...
The state of IRPGO (3 remaining work items)
2016 May 25
2
The state of IRPGO (3 remaining work items)
...my 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 as a byproduct results in a huge volume of warnings). &...
The state of IRPGO (3 remaining work items)
2016 Jun 01
4
The state of IRPGO (3 remaining work items)
...d 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 as a byproduct results in a huge volume of warnings). > > > > This can...
The state of IRPGO (3 remaining work items)
2016 Jun 02
2
The state of IRPGO (3 remaining work items)
...ses 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 as a byproduct results in a huge volume of warnings). >> > >> >...
The state of IRPGO (3 remaining work items)
2016 Jun 02
4
The state of IRPGO (3 remaining work items)
...ssues 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 as a byproduct results in a huge volume of warnings). >>> > >>&g...
The state of IRPGO (3 remaining work items)
2016 Jun 03
5
The state of IRPGO (3 remaining work items)
...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 as a byproduct resu...
The state of IRPGO (3 remaining work items)
2016 Jun 13
2
The state of IRPGO (3 remaining work items)
...t;>>> 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...
The state of IRPGO (3 remaining work items)
2016 Jun 23
0
The state of IRPGO (3 remaining work items)
...lso 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 as a by...