public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "habbit89 at hotmail dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110626] Duplicated finalization in derived Date: Tue, 11 Jul 2023 10:27:38 +0000 [thread overview] Message-ID: <bug-110626-4-cyi7rX1BWq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110626-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110626 --- Comment #2 from Javier Martín <habbit89 at hotmail dot es> --- Note: when I said that the output of gfortran-11 is "correct", it is in reference to this specific issue. In particular, the output of gfortran-11 seems to be affected by bug 105170, which is a separate problem with assignment and finalization of derived types. However, that bug appears to be fixed in the finalization changes for gfortran-13.
prev parent reply other threads:[~2023-07-11 10:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 9:40 [Bug fortran/110626] New: " habbit89 at hotmail dot es 2023-07-11 9:46 ` [Bug fortran/110626] " habbit89 at hotmail dot es 2023-07-11 10:27 ` habbit89 at hotmail dot es [this message]
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-110626-4-cyi7rX1BWq@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).