This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Proposal to add FDO profile quality related diagnostics
- From: Andi Kleen <ak at linux dot intel dot com>
- To: Indu Bhagat <indu dot bhagat at oracle dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 20 Nov 2018 19:47:48 -0800
- Subject: Re: Proposal to add FDO profile quality related diagnostics
- References: <95e2b69c-6285-6dd5-2f08-c6ded425ed43@oracle.com>
Indu Bhagat <indu.bhagat@oracle.com> 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 programs
have a lot of cold error handling functions etc. that are never executed
in a normal execution.
Like how does it look like for a gcc build for example?
I suspect it would need some heuristics to cut it down at least, like if
the function ends with exit (perhaps propagated through the call tree)
it's not flagged. Or if there is warning for a function don't warn
about callees that are not called from somewhere else.
-Andi