https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84684
--- Comment #11 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Seems like another of the wrong caching issues. I can't reproduce it on my laptop though; can you figure out where the first call, the one which ends up cached in the constexpr_call_table originates?
