public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/102094] d: ICE in gimple_register_canonical_type_1, at lto/lto-common.c:430 Date: Sun, 29 Aug 2021 16:31:11 +0000 [thread overview] Message-ID: <bug-102094-4-sYXLFOfhPf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102094-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102094 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:07984707be4eb9aea55dafbbc796790b8b8ac700 commit r12-3206-g07984707be4eb9aea55dafbbc796790b8b8ac700 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Sat Aug 28 16:57:03 2021 +0200 d: ICE in gimple_register_canonical_type_1, at lto/lto-common.c:430 (PR102094) User defined types have the TYPE_CXX_ODR_P flag set, but closure frames did not. This mismatch led to an ICE in the conflict detection for ODR and interoperable non-ODR types. As a given closure frame is tied explicitly to a function, it already conforms to ODR. PR d/102094 gcc/d/ChangeLog: * d-codegen.cc (build_frame_type): Set TYPE_CXX_ODR_P. gcc/testsuite/ChangeLog: * gdc.dg/lto/pr102094_0.d: New test.
next prev parent reply other threads:[~2021-08-29 16:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-27 11:15 [Bug d/102094] New: " ibuclaw at gcc dot gnu.org 2021-08-28 14:46 ` [Bug d/102094] " ibuclaw at gdcproject dot org 2021-08-29 16:31 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-29 16:32 ` ibuclaw at gdcproject dot 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-102094-4-sYXLFOfhPf@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).