pub struct Counts { /* private fields */ }Expand description
What the queries did, which is the only way to find out that this is not working.
A range that came back knowing nothing produces correct code that is slower, with no test
failing and no warning printed. Section 10.7 says the defence is a counter and section 10.8
says -ftime-report prints it.
Implementations§
Source§impl Counts
impl Counts
Sourcepub const fn fallbacks(&self) -> u64
pub const fn fallbacks(&self) -> u64
How many were answered with the range at the definition because the cache was full.
Sourcepub const fn exhausted(&self) -> u64
pub const fn exhausted(&self) -> u64
How many came back knowing nothing because the budget was spent.
These are the ones section 10.7 is really about. A range that lost the information at an
opcode is a gap in the transfer functions and shows up in Counts::losses. A range that
never got worked out at all shows up nowhere else, and a function whose count here is not
zero is a function every pass downstream is optimizing blind.