From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CB0923851145; Fri, 24 Feb 2023 16:37:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CB0923851145 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677256649; bh=sUSRFYrNf4/5XIu9pR6w/hMeHSoeqBCfkRGonS0VeEc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nmBXMBrAng+hZLF4qwZ/3ny30oLGshAcw+LmPM6rwEOWcAfhOCKNaaNyXI2oAc5jw ArqhZSyz6QaYZDl3Y5RPisKfS7NZRDmNXCnlJ93i0BChAjuCnbRbp3W/LwmIUTeDf+ emo9rEaNIeykfEcyKbMJilfHRcACmqhjK8bNn5XM= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108924] memory leak in doloop_warn Date: Fri, 24 Feb 2023 16:37:29 +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: anlauf 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: cc attachments.created Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108924 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #1 from anlauf at gcc dot gnu.org --- Created attachment 54532 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54532&action=3Dedit Tentative patch Does the attached fix this? Without a testcase this seems to be the fix obtained from reviewing the surrounding code. Regtests cleanly here.=