https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- Unfortunately, without a somewhat reduced test case, there is not a lot I can do :-( Could you run this under valgrind, pinpoint the memory leaks (somewhat) and then try to reduce this?
