--- Comment #8 from Jan Hubicka <hubicka at gcc dot> ---
I see. compute_uninlined_call_time uses counts when they are available and
frequencies when they are not.  It makes sense that dropping count to 0 will
lead to change of compute_uninlined_call_time. I am bit surprised it is that
large (it would be nice to know why).

Otherwise I have WIP path that gets rid of frequencies completely, so it will
fix this problem.  I will try to finish it soon.

Thanks a lot for looking into this!

Reply via email to