Proposal to add diagnostics to know which functions were not run in the
training run in FDO.
Motivation :
When using FDO, it is often desirable to know the quality of function profile.
This means knowing which functions have STALE, NO/MISSING or ZERO profiles. GCC
has diagnostics for STALE (Wcove
cteristics.
Thanks
Indu
On 11/22/2018 03:58 AM, Martin Liška wrote:
On 11/21/18 4:47 AM, Andi Kleen wrote:
Indu Bhagat writes:
Proposal to add diagnostics to know which functions were not run in the
training run in FDO.
Don't you think the warning will be very noisy? I assume most program
[Trying to get some feedback. I earlier posted on gcc-help a week ago]
In tree.def -
/* Minimum and maximum values. When used with floating point, if both
operands are zeros, or if either operand is NaN, then it is unspecified
which of the two operands is returned as the result. */
DEFTRE
Wcoverage-mismatch is meant to "Warn in case profiles in -fprofile-use do not
match"
Currently, gcc compiler warns about the following two cases of source code
changes which alert the programmer to re-generate the profiles :
1. Control flow mismatch
If functions' control flow has been altered
On 08/13/2018 06:32 AM, Martin Liška wrote:
On 08/09/2018 08:05 PM, Indu Bhagat wrote:
Wcoverage-mismatch is meant to "Warn in case profiles in -fprofile-use do not
match"
Currently, gcc compiler warns about the following two cases of source code
changes which alert the progra
Can I get some updates on this please? Is the public version up for use?
Thanks!
Indu
On Thu, Jul 19, 2007 at 10:32 PM, Rask Ingemann Lambertsen
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Jul 19, 2007 at 04:41:50PM +0200, Indu Bhagat wrote:
> > Hi,
> >
> > I need to stud
Hi,
I need to study 16-bit binaries (Intel based architecture) for
research purposes.I will appreciate if someone could let me know some
details of the project on "Porting GCC to Intel 16-bit architecture".
Particularly,
1) Support level : few words on the unsupported stuff and basic
assumptions
