https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99479
--- Comment #21 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Patrick Palka from comment #20) > Using a non-static vector fixes the valgrind error. Is this a fix that's > worth applying at this point? I do think it might fix a bunch of modules issues where the ICE can come and go. Maybe when GCC 12 branches off, we remove the static but keep this bug report open and see if there is a way to fix this for GCC 13? The number of ICEs reported against modules keep on growing as more people are using it and getting rid of the biggest memory corruption issue will at least allow more people to test out modules in my mind.
