[Bug fortran/109010] New: Fortran frontend memory leaks building SPEC CPU 2017

[Bug fortran/109010] New: Fortran frontend memory leaks building SPEC CPU 2017

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109010

            Bug ID: 109010
           Summary: Fortran frontend memory leaks building SPEC CPU 2017
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

Building the benchmark set fprate_any_fortran of SPEC CPU 2017 with -Ofast
-march=znver2 using valgrind with --leak-check=full still reveals a lot of
leaks.

[Bug fortran/109010] Fortran frontend memory leaks building SPEC CPU 2017

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109010

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I've tried to attach the full build log but it's too large even compressed.
Instead I placed it at https://gcc.opensuse.org/CPU2017.449.log.xz but it
might take a day or so for it to appear.

Not all leaks might be easy to fix, but
for example looking for __gmp_default_allocate reveals leaked GMP variables.
I guess adding RAII class wrapper(s) might be a good cleanup opportunity here.

Likewise gfc_expr_walker, used by frontend passes point to places that might
leak memory not on the order of the number of source statements.