public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jhaiduce at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97024] Overriding finalization on polymorphic types triggers ICE error in generate_finalization_wrapper Date: Fri, 11 Sep 2020 18:13:28 +0000 [thread overview] Message-ID: <bug-97024-4-Kz0EbhAvnx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97024-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97024 --- Comment #1 from John Haiducek <jhaiduce at gmail dot com> --- This bug shows some similarity to 92587 and 82996, but I suspect they are distinct. 92587 had a much more complicated MWE and the OP was unable to reduce it to a single file. 82996 did not involve class polymorphism, which seems to be required to trigger this bug. Someone with better knowledge of the compiler might be able to identify a common cause however.
next prev parent reply other threads:[~2020-09-11 18:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-11 18:05 [Bug fortran/97024] New: " jhaiduce at gmail dot com 2020-09-11 18:13 ` jhaiduce at gmail dot com [this message] 2020-09-11 18:16 ` [Bug fortran/97024] " jhaiduce at gmail dot com 2020-12-02 20:58 ` dominiq at lps dot ens.fr 2022-01-29 8:36 ` pault 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-97024-4-Kz0EbhAvnx@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).