__builtin_expect
from GCC can be used by programmer to show which variants are expected to be very often and which are rare. But __builtin_expect
have only "true" and "false" (0% or 100% probability)
For some big projects it is vary hard to get profile feedback (-fprofile-arcs
), and sometimes programmer does know, what probability of branch he have in some point of program.
It is possible to give a hint to compiler that a branch have probability >0% and <1开发者_运维百科00% ?
From here:
long __builtin_expect_with_probability
(long exp, long c, double probability) The function has the same semantics as
__builtin_expect
, but caller provides the expected probability thatexp == c
. Last argument, probability, is a floating-value in the inclusive range 0.0f and 1.0f. The probability argument must be constant floating-point expression.
Jesin pointed out in the comments, Clang 11 has it too.
True and false really mean that "the first variant is more likely" and "the second variant is more likely". There's no practical need for any values other than these. The compiler won't be able to use that information.
Non-determinism is not a desirable trait for compiler output, let alone language features. There is no real benefit to only partial optimization preferring one branch, and no compiler I'm aware of can do this.
精彩评论