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/110576] ICE on compilation Date: Wed, 12 Jul 2023 19:19:51 +0000 [thread overview] Message-ID: <bug-110576-4-8eX66RrpbC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110576-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110576 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords| |ice-on-valid-code CC| |anlauf at gcc dot gnu.org Last reconfirmed| |2023-07-12 --- Comment #5 from anlauf at gcc dot gnu.org --- ICE confirmed for all versions tested (>= 7 ... 14-trunk). (gdb) l 9222 9223 bool is_pdt_type = c->ts.type == BT_DERIVED 9224 && c->ts.u.derived->attr.pdt_type; 9225 9226 cdecl = c->backend_decl; 9227 ctype = TREE_TYPE (cdecl); 9228 9229 switch (purpose) 9230 { 9231 (gdb) p c->name $5 = 0x15555449f100 "i_mci" (gdb) p c->backend_decl $6 = (tree) 0x0 The "i_mci" is a component of type process_mci_entry_t, not a local variable. This is better seen with a slightly further reduced reproducer.
next prev parent reply other threads:[~2023-07-12 19:19 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-06 16:38 [Bug fortran/110576] New: " juergen.reuter at desy dot de 2023-07-11 17:16 ` [Bug fortran/110576] " juergen.reuter at desy dot de 2023-07-11 17:19 ` juergen.reuter at desy dot de 2023-07-11 22:49 ` juergen.reuter at desy dot de 2023-07-11 22:50 ` juergen.reuter at desy dot de 2023-07-12 19:19 ` anlauf at gcc dot gnu.org [this message] 2023-07-12 19:22 ` anlauf at gcc dot gnu.org 2023-07-12 19:41 ` [Bug fortran/110576] ICE in structure_alloc_comps, at trans-array.cc:9227 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-110576-4-8eX66RrpbC@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).