From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 523C23858D34; Mon, 27 Apr 2020 17:36:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 523C23858D34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1588008988; bh=5Wz23NGQ8S8aK0OBkn/kX1nf3HdAvAGI9ViBskukTpA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XCKVu6eEGqBH1VaRyNsWxx1uHLeUjEuFWHq0PdvwpzBqt4FzdE1CXQsE7c9FKDQ25 E12vA/+C4HUR2mb8wH5F3xvv3e8KtqYTljmkp6B0w9LVqpRq3oTWycyDMl0Fn+Q11o xRx9HsdFFIkT3d1tRKsDCQKBjvf2ngKiquMpMgqo= From: "juergen.reuter at desy dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/94788] [10 Regression] Severe regression leading to double free in tcache Date: Mon, 27 Apr 2020 17:36:28 +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: 10.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: juergen.reuter at desy dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.0 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: Mon, 27 Apr 2020 17:36:28 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94788 --- Comment #9 from J=C3=BCrgen Reuter --- (In reply to Thomas Koenig from comment #8) > I'd like to understand what went wrong here... I suspect that > the fix exposed another bug somewhere :-( >=20 > Is it possible to isolate a test case like that? If that is > the offending patch, I think it is probably about a pointer to a > variable of a derived type, either via a function or as > an argument (look at the test case to see what the patch > fixes). I'm on the way to condense the reproducer. At latest tomorrow you will get = it. I really hope we get this fixed before the gcc 10 release.=