public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <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: Wed, 29 Apr 2020 21:58:00 +0000	[thread overview]
Message-ID: <bug-94788-4-KpmiX8eFgC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94788-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #34 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Created attachment 48411
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48411&action=edit
Final reproducer, less than 300 lines ;)

This one should be sufficient. No further files or input is necessary, it seems
that the problem lies in the combination of inheriting derived types,
allocatables and pointers. All the fun.

  parent reply	other threads:[~2020-04-29 21:58 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  8:38 [Bug fortran/94788] New: " juergen.reuter at desy dot de
2020-04-27  8:38 ` [Bug fortran/94788] " juergen.reuter at desy dot de
2020-04-27  9:46 ` juergen.reuter at desy dot de
2020-04-27 10:27 ` [Bug fortran/94788] [10 Regression] " rguenth at gcc dot gnu.org
2020-04-27 10:41 ` juergen.reuter at desy dot de
2020-04-27 12:19 ` juergen.reuter at desy dot de
2020-04-27 12:49 ` simon.brass at desy dot de
2020-04-27 17:09 ` simon.brass at desy dot de
2020-04-27 17:26 ` tkoenig at gcc dot gnu.org
2020-04-27 17:36 ` juergen.reuter at desy dot de
2020-04-27 18:30 ` tkoenig at gcc dot gnu.org
2020-04-27 19:26 ` juergen.reuter at desy dot de
2020-04-27 19:33 ` juergen.reuter at desy dot de
2020-04-27 20:39 ` juergen.reuter at desy dot de
2020-04-27 20:40 ` juergen.reuter at desy dot de
2020-04-27 20:40 ` juergen.reuter at desy dot de
2020-04-27 21:15 ` juergen.reuter at desy dot de
2020-04-27 21:38 ` tkoenig at gcc dot gnu.org
2020-04-27 21:51 ` cvs-commit at gcc dot gnu.org
2020-04-27 21:55 ` [Bug fortran/94788] [8/9 " tkoenig at gcc dot gnu.org
2020-04-27 22:02 ` juergen.reuter at desy dot de
2020-04-27 22:23 ` kargl at gcc dot gnu.org
2020-04-27 22:33 ` juergen.reuter at desy dot de
2020-04-28  5:57 ` tkoenig at gcc dot gnu.org
2020-04-28  8:02 ` burnus at gcc dot gnu.org
2020-04-28  8:12 ` juergen.reuter at desy dot de
2020-04-28  8:17 ` juergen.reuter at desy dot de
2020-04-28  9:13 ` tkoenig at gcc dot gnu.org
2020-04-28 11:17 ` juergen.reuter at desy dot de
2020-04-28 11:36 ` juergen.reuter at desy dot de
2020-04-28 14:06 ` juergen.reuter at desy dot de
2020-04-29  0:38 ` juergen.reuter at desy dot de
2020-04-29  9:09 ` juergen.reuter at desy dot de
2020-04-29 18:32 ` tkoenig at gcc dot gnu.org
2020-04-29 21:58 ` juergen.reuter at desy dot de [this message]
2020-04-30 16:31 ` tkoenig at gcc dot gnu.org
2020-04-30 16:35 ` juergen.reuter at desy dot de
2020-04-30 16:49 ` tkoenig at gcc dot gnu.org
2020-04-30 17:37 ` juergen.reuter at desy dot de
2020-04-30 17:38 ` juergen.reuter at desy dot de
2020-05-01 12:27 ` tkoenig at gcc dot gnu.org
2020-05-01 12:53 ` cvs-commit at gcc dot gnu.org
2020-05-01 12:55 ` cvs-commit at gcc dot gnu.org
2020-05-02 15:33 ` cvs-commit at gcc dot gnu.org
2020-05-02 19:51 ` cvs-commit at gcc dot gnu.org
2020-05-21 10:42 ` tkoenig at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94788-4-KpmiX8eFgC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).