public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99585] ICE with SIZE intrinsic on nested derived type components Date: Sun, 14 Mar 2021 19:46:33 +0000 [thread overview] Message-ID: <bug-99585-4-GqBU4pO7nn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99585-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99585 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 Keywords| |ice-on-valid-code Last reconfirmed| |2021-03-14 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Known to fail| |10.2.1, 11.0, 7.5.0, 8.4.1, | |9.3.1
next prev parent reply other threads:[~2021-03-14 19:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-14 19:45 [Bug fortran/99585] New: " anlauf at gcc dot gnu.org 2021-03-14 19:46 ` anlauf at gcc dot gnu.org [this message] 2021-03-14 20:27 ` [Bug fortran/99585] " anlauf at gcc dot gnu.org 2021-03-14 21:06 ` anlauf at gcc dot gnu.org 2021-03-15 9:07 ` marxin at gcc dot gnu.org 2022-03-07 21:12 ` cvs-commit at gcc dot gnu.org 2022-03-19 7:49 ` cvs-commit at gcc dot gnu.org 2023-08-27 19:48 ` 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-99585-4-GqBU4pO7nn@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).