Function mul_erratum_triggers 

pub fn mul_erratum_triggers(prev_a: f64, prev_b: f64) -> bool

Would the erratum’s trigger condition fire for this multiply?

True when an operand of the previous multiply was a NaN, zero or infinity. Exposed so a future characterization has a tested trigger to hang the corrupted output on, and so a trace can flag affected instructions today.