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/106047] ICE in structure_alloc_comps, at fortran/trans-array.cc:9574 Date: Wed, 22 Jun 2022 20:44:19 +0000 [thread overview] Message-ID: <bug-106047-4-IILnm9u0IN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106047-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106047 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-06-22 Ever confirmed|0 |1 CC| |anlauf at gcc dot gnu.org --- Comment #1 from anlauf at gcc dot gnu.org --- ICE confirmed. But it is really invalid? Intel & NAG accept it. Part of the problem is gfc_element_size. It calculates a number that is 8 for -m64, and 4 for -m32, likely sizeof (gfc_charlen_t), instead of noticing that we have a descriptor for deferred length character. (OTOH using character, allocatable :: c(:) seems to work, so maybe the real issue is in gfc_typenode_for_spec).
next prev parent reply other threads:[~2022-06-22 20:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-21 18:49 [Bug fortran/106047] New: " gscfq@t-online.de 2022-06-22 20:44 ` anlauf at gcc dot gnu.org [this message] 2022-06-23 15:41 ` [Bug fortran/106047] " gscfq@t-online.de 2022-06-24 6:12 ` gscfq@t-online.de
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-106047-4-IILnm9u0IN@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).