From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 889883870854; Wed, 3 Jun 2020 14:55:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 889883870854 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591196112; bh=2rbYFs/fAcFIgGmWVvJ3W6L0Dwl6VGrU6neBZMNHCaE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ej0ZZqFr0+W/7vQi19vxfYqUL/K7zB1xYu1aSC30BK+UhUgE16s588Vmmc23JywxM Qv3TdSrr+SDKMz+2+c+t9HuwZbrjsOVK+6nr3+7vMbDCCxcZFrk0CQ9PgI362GxL4J UNiUEh5n7RxVFedjlaVX1SSMrNXphPDfooLbDk38= From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/94109] Memory leak introduced in 8.3.0->8.3.1 Date: Wed, 03 Jun 2020 14:55:12 +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: 8.3.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: WAITING 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: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 14:55:12 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94109 --- Comment #10 from Thomas Koenig --- (In reply to Dominique d'Humieres from comment #9) > Is it a false positive or not? You probably need a higher optimization level with -fanalyzer, it doesn't show anything at -O. Nor does valgrind show anything. So, I'd say a false positive.=