https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117100
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Created attachment 59325 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59325&action=edit Patch which might fix the issue Can you test this patch? It might fix the issue by using an allocated array of int_range_max instead of a auto_vec<int_range_max> . vec does not call the constructor or deconstructor so we might even be leaking memory.
