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/106731] ICE on automatic array of derived type with DTIO Date: Sat, 21 Jan 2023 23:13:57 +0000 [thread overview] Message-ID: <bug-106731-4-QFSn844DOr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106731-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #15 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Backport complete, closing.
prev parent reply other threads:[~2023-01-21 23:13 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-24 7:44 [Bug fortran/106731] New: " federico.perini at gmail dot com 2022-08-24 7:49 ` [Bug fortran/106731] " marxin at gcc dot gnu.org 2022-08-24 8:22 ` federico.perini at gmail dot com 2022-08-24 17:38 ` kargl at gcc dot gnu.org 2022-08-24 19:10 ` federico.perini at gmail dot com 2022-08-24 19:27 ` sgk at troutmask dot apl.washington.edu 2022-08-25 7:16 ` federico.perini at gmail dot com 2022-11-08 21:11 ` anlauf at gcc dot gnu.org 2022-12-23 3:13 ` jvdelisle at gcc dot gnu.org 2022-12-23 3:47 ` jvdelisle at gcc dot gnu.org 2022-12-23 5:21 ` cvs-commit at gcc dot gnu.org 2022-12-23 20:42 ` federico.perini at gmail dot com 2023-01-17 20:52 ` anlauf at gcc dot gnu.org 2023-01-18 1:00 ` jvdelisle at gcc dot gnu.org 2023-01-21 23:09 ` cvs-commit at gcc dot gnu.org 2023-01-21 23:13 ` jvdelisle at gcc dot gnu.org [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-106731-4-QFSn844DOr@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).