From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 025313858C5E; Fri,  3 Mar 2023 14:15:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 025313858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677852953;
	bh=myWEkx0ACmdEa6t5cEc78WwQVUnbaej0vcol0GBhE5g=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=MmxQ4WvGJkf9VRJbkIK+rsHuewt6CF2G1okYpbKnsJoD4CxdfalRT/qq5QMYcZ3iH
	 HuvKzdmtgs76OO9LEMvth2p31f/iIBvxvp1vc0G0WaFvNVp7UWn5YrbXin9oIbxrgi
	 ecIqrdkxJ9zTx76jPwDSo/Mvv52Z2D5AoomJVY1k=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109010] Fortran frontend memory leaks building SPEC CPU
 2017
Date: Fri, 03 Mar 2023 14:15:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109010-4-iZgjJqQNGl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- 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 he=
re.

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.=