public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105800] Segfault deallocating a class, dimension(:) array Date: Fri, 14 Apr 2023 05:07:21 +0000 [thread overview] Message-ID: <bug-105800-4-tiQaKU2Y1x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105800-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105800 --- Comment #1 from martin <mscfd at gmx dot net> --- Created attachment 54856 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54856&action=edit fixed testcase class_dealloc.f90 As I just see, the first attachment does not show the bug as return value "a" of function create is declared as "class(t), dimension(:), pointer". And as described in the initial report, with class instead of type, there is no error. The fixed attachment declares "a" as "type(t), dimension(:), pointer". This shows the described error. It is still present in the current 13 development branch.
next prev parent reply other threads:[~2023-04-14 5:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-01 9:44 [Bug fortran/105800] New: " mscfd at gmx dot net 2023-04-14 5:07 ` mscfd at gmx dot net [this message] 2023-04-14 19:20 ` [Bug fortran/105800] " anlauf 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-105800-4-tiQaKU2Y1x@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).