public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m101010a at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108116] New: internal compiler error: in check_noexcept_r, at cp/except.cc:1074 Date: Thu, 15 Dec 2022 02:05:21 +0000 [thread overview] Message-ID: <bug-108116-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108116 Bug ID: 108116 Summary: internal compiler error: in check_noexcept_r, at cp/except.cc:1074 Product: gcc Version: 12.2.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m101010a at gmail dot com Target Milestone: --- When compiling the code #include <initializer_list> struct c { c(int); ~c(); }; struct d { d(std::initializer_list<c>); }; struct e { d f{0}; }; template <typename> void h() { e{}; } GCC 12 fails with an internal compiler error. This happens with GCC 12.1, 12.2, and when built off of the recent git commit f17ddf2c484427e6ddfd994b62fefcdac27ac02f. It does not happen with GCC 11.3 or before. The full error details and preprocessed source are in the attachment.
next reply other threads:[~2022-12-15 2:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-15 2:05 m101010a at gmail dot com [this message] 2022-12-15 2:07 ` [Bug c++/108116] " m101010a at gmail dot com 2022-12-15 10:48 ` [Bug c++/108116] [12/13 Regression] ICE in check_noexcept_r, at cp/except.cc:1074 since r12-6897-gdec8d0e5fa00ceb2 marxin at gcc dot gnu.org 2022-12-15 10:50 ` marxin at gcc dot gnu.org 2022-12-15 22:27 ` pinskia at gcc dot gnu.org 2022-12-20 19:57 ` ppalka at gcc dot gnu.org 2022-12-21 12:42 ` rguenth at gcc dot gnu.org 2022-12-23 16:18 ` cvs-commit at gcc dot gnu.org 2022-12-23 16:18 ` [Bug c++/108116] [12 " ppalka at gcc dot gnu.org 2023-03-07 2:18 ` cvs-commit at gcc dot gnu.org 2023-03-07 2:23 ` ppalka 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-108116-4@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).