public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stevenxia990430 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110065] New: auto in template argument causes ICE, also accepts-invalid Date: Wed, 31 May 2023 18:19:01 +0000 [thread overview] Message-ID: <bug-110065-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110065 Bug ID: 110065 Summary: auto in template argument causes ICE, also accepts-invalid Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: stevenxia990430 at gmail dot com Target Milestone: --- The following program produces internal compiler error: Segmentation fault. Tested on GCC-trunk To quickly reproduce: https://gcc.godbolt.org/z/noY1qxK91 ``` #include <type_traits> #include <iostream> auto main() -> int { std::cout << std::is_scoped_enum_v<auto(&)(const int*) -> auto&>; return EXIT_SUCCESS; } ``` Note, if we remove the std::cout and produce the following code: ``` #include <type_traits> #include <iostream> auto main() -> int { std::is_scoped_enum_v<auto(&)(const int*) -> auto&>; return EXIT_SUCCESS; } ``` gcc compiles without any error, however this code is rejected by Clang (tested on Clang-trunk)
next reply other threads:[~2023-05-31 18:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 18:19 stevenxia990430 at gmail dot com [this message] 2023-05-31 21:54 ` [Bug c++/110065] " pinskia at gcc dot gnu.org 2023-05-31 21:56 ` [Bug c++/110065] [11/12/13/14 Regression] [C++20/2b] " pinskia at gcc dot gnu.org 2024-01-10 15:53 ` [Bug c++/110065] [11/12/13/14 Regression] [C++20/2b] auto return type " jamborm at gcc dot gnu.org 2024-01-11 23:28 ` mpolacek at gcc dot gnu.org 2024-01-12 13:46 ` mpolacek at gcc dot gnu.org 2024-01-12 14:05 ` rguenth at gcc dot gnu.org 2024-01-15 19:50 ` mpolacek at gcc dot gnu.org 2024-01-15 23:40 ` cvs-commit 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-110065-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).