On Sep 30, 2015, at 1:04 AM, Richard Biener <richard.guent...@gmail.com> wrote: > So what about a branch_cost hook that takes taken/not-taken probabilities as > argument?
So, for my port, I need to know %prediction as well to calculate cost. I know, kinda sucks. Or put another way, I want to explain the cost taken, predicted, not-taken, predicted, taken, mis-predicted, and not-taken-mis-predicted and let the caller sort out if the branch will be predicted or mis-predicted, as it can do the math itself and that math is target independent.
