This regression slipped in because my testing was a week old. The predict-22.c is a commit of Nov 28.

Thanks Jeff. I saw this regression yesterday and was about to send the patch shortly.

I should have kept the patch tested proactively.

Thanks

Indu


On 12/01/2018 08:56 AM, Jeff Law wrote:

Indu's change to clean up some profiling dumps clearly wasn't regression
tested as it fails on every target.

We have an edge to a block with a call to an explicitly marked cold
function in it.  We consider that a precise prediction.

Indu's change reflects that information into the dump file, changing it
from "count 0," to "count 0 (precise),".

This change fixes the test.  Indu, please do a regression test on your
changes.  That's standard procedure to avoid this kind of problem.

Installing on the trunk.

jeff

Reply via email to