Hi,
I proofread the code and noticed that in some cases I may trigger division by 0
that may
get different outputs depending on optimization setting on Itanium.
This is what I comitted after profiledbootstrap and regtesting at x86_64.
* profile-count.h (apply_probability,
apply_s
On Jun 19 2017, Jan Hubicka wrote:
> this patch makes us to track quality of the profile. This is useful
> to disable some agressive optimizations when counts are known to be
> unreliable.
This breaks bootstrap on ia64 with a comparison failure in value-prof.o.
The only difference is in gimple
