public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michsteinb at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105289] New: ICE on partial specialization Date: Fri, 15 Apr 2022 22:59:46 +0000 [thread overview] Message-ID: <bug-105289-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105289 Bug ID: 105289 Summary: ICE on partial specialization Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: michsteinb at gmail dot com Target Milestone: --- Created attachment 52818 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52818&action=edit Self-contained reproduction of the ICE, compile with -std=c++20 arm-none-eabi-g++ 11.2 crashes on attached self-contained code with following prompt on win64: ``` PS H:\projects\install\arm-embedded-gcc\11.2-2022.02\bin> .\arm-none-eabi-g++.exe -save-temps -std=c++20 -c repro.cxx repro.cxx:14:8: internal compiler error: Segmentation fault 14 | struct push_front_vlist<XList<T, Vs...>, Arg> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Please submit a full bug report, with preprocessed source if appropriate. See <https://bugs.linaro.org/> for instructions. ``` The 10.x release cycle compilers accepted this code, so does clang, so this is a regression introduced with 11.0. Further checks on godbolt showed the same behaviour on all 11.x compilers I tried. The problem stems from the primary template using a meta-function of its first parameter as type for its second. If I do not constrain the type of Arg, the crash disappears.
next reply other threads:[~2022-04-15 22:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-15 22:59 michsteinb at gmail dot com [this message] 2022-04-18 18:24 ` [Bug c++/105289] [11/12 Regression] " ppalka at gcc dot gnu.org 2022-04-19 9:23 ` rguenth at gcc dot gnu.org 2022-04-22 19:13 ` michsteinb at gmail dot com 2022-04-26 1:49 ` cvs-commit at gcc dot gnu.org 2022-04-26 15:19 ` ppalka at gcc dot gnu.org 2022-04-26 15:19 ` [Bug c++/105289] [11 " ppalka at gcc dot gnu.org 2022-04-26 16:13 ` michsteinb at gmail dot com 2022-04-28 15:39 ` cvs-commit at gcc dot gnu.org 2023-05-21 14:13 ` 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-105289-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).