public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "baradi09 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105170] Invalid finalization in intrinsic assignment Date: Fri, 08 Dec 2023 15:34:16 +0000 [thread overview] Message-ID: <bug-105170-4-Ht15jDsrnX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105170-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105170 --- Comment #2 from Bálint Aradi <baradi09 at gmail dot com> --- Thanks, with 13.2.0, it seems to behave correctly.
prev parent reply other threads:[~2023-12-08 15:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 19:58 [Bug fortran/105170] New: " baradi09 at gmail dot com 2023-12-07 21:26 ` [Bug fortran/105170] " anlauf at gcc dot gnu.org 2023-12-08 15:34 ` baradi09 at gmail dot com [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-105170-4-Ht15jDsrnX@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).