https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115639
--- Comment #5 from Patrick Palka <ppalka at gcc dot gnu.org> --- (In reply to Patrick Palka from comment #4) > (In reply to Jason Merrill from comment #3) > > (In reply to Marek Polacek from comment #2) > > > The second time around, we're not finding the call in > > > constexpr_call_table. > > > > We can't reuse the result due to the different value of mce; the first time > > we have mce_unknown, the second time mce_true. > It should be feasible to reuse a cached call result across different mce > values if we track whether result is independent of the mce value, i.e. if > evaluation of the call doesn't depend on another call that is sensitive to > mce. ... 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?
