public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding Date: Fri, 03 Feb 2023 02:21:59 +0000 [thread overview] Message-ID: <bug-108649-4-GpcYpNzH7g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108649-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |jvdelisle at gcc dot gnu.org Last reconfirmed| |2023-02-03 Status|UNCONFIRMED |NEW --- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Thanks for giving test cases. I have not looked in detail but I will say that finalization bugs are being actively worked by Paul Thomas. He is very close to having it ready. I will try you cases against his latest patch to see what happens.
next prev parent reply other threads:[~2023-02-03 2:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-03 0:07 [Bug fortran/108649] New: " Boyce at engineer dot com 2023-02-03 0:20 ` [Bug fortran/108649] " Boyce at engineer dot com 2023-02-03 0:21 ` Boyce at engineer dot com 2023-02-03 0:21 ` Boyce at engineer dot com 2023-02-03 0:21 ` Boyce at engineer dot com 2023-02-03 0:24 ` Boyce at engineer dot com 2023-02-03 2:21 ` jvdelisle at gcc dot gnu.org [this message] 2023-02-03 16:19 ` Boyce at engineer dot com 2023-02-03 16:22 ` Boyce at engineer dot com
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-108649-4-GpcYpNzH7g@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: linkBe 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).