https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115639
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Patrick Palka from comment #5) > ... and in particular if we have a cached mce_unknown call result it means > the call isn't sensitive to mce, and so we can reuse later when evaluating > the call with mce_true or mce_false? Good point, if the first constexpr_call_table->find_slot doesn't find a value we could try again with mce_unknown.
