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 0C4D63851C1E; Tue, 28 Apr 2020 05:57:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C4D63851C1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1588053437;
 bh=6ag6sTpsdBIzWdqzrvCetREzB3Y7/FPrgW/Qr/WcfUI=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=PEKGZkGoeJfCSsFYKAY6hJeyU8/tXqUONEyc1AG71nH1/xXaGgSOCBff+j7oYryPF
 DUhbuyDW4ZVc+gFWCBBLwfqUNR/zJBYVINHeDmiE4+9mQsuINnDBLOutfrfE/kZOS7
 CbwibQ5DRb6c9bWzVnN4nDDLL0lKfwptsUkW2nRE=
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94788] [8/9 Regression] Severe regression leading to
 double free in tcache
Date: Tue, 28 Apr 2020 05:57:16 +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: 9.3.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status blocked
Message-ID: <bug-94788-4-KA2BgXnPyz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94788-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2020 05:57:17 -0000

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
             Blocks|                            |93956

--- Comment #23 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to J=C3=BCrgen Reuter from comment #20)
> Thanks a lot for reverting, Thomas, shall I further reduce the reproducer,
> or can you work with it now?

I could use it to confirm that there is a bug, but the test case is
far too complex for analysis, and it is also not possible to put
it in the testsuite.  So, at the moment, work on PR 93956 (a F95 wrong-code
bug, hence a high priority) is effectively blocked.

So yes, I would appreciate a shorter reproducer, especially since
I plan to revisit the whole span and pointer area once gcc 10
is out of the door.

So, I'll mark this bug as WAITING for now.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93956
[Bug 93956] Wrong array creation with p =3D> array_dt(1:n)%component=