public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100055] New: ICE on invalid requires expression Date: Mon, 12 Apr 2021 23:10:29 +0000 [thread overview] Message-ID: <bug-100055-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100055 Bug ID: 100055 Summary: ICE on invalid requires expression Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ldalessandro at gmail dot com Target Milestone: --- The following invalid code triggers a segfault. ``` void foo(auto&& arg) requires({}); <source>:1:30: error: statement-expressions are not allowed outside functions nor in template-argument lists 1 | void foo(auto&& arg) requires({}); | ^ <source>:1:33: internal compiler error: Segmentation fault 1 | void foo(auto&& arg) requires({}); | ^ 0x1d01009 internal_error(char const*, ...) ???:0 0x7a1b17 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*, decl_context, int, tree_node**) ???:0 0x7a7a78 start_decl(cp_declarator const*, cp_decl_specifier_seq*, int, tree_node*, tree_node*, tree_node**) ???:0 0x8e230d c_parse_file() ???:0 0xa615b2 c_common_parse_file() ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. ASM generation compiler returned: 1 ``` live example: https://godbolt.org/z/qjWWWchjo
next reply other threads:[~2021-04-12 23:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-12 23:10 ldalessandro at gmail dot com [this message] 2021-04-22 16:35 ` [Bug c++/100055] " mpolacek at gcc dot gnu.org 2021-04-22 16:41 ` [Bug c++/100055] [10/11/12 Regression] " mpolacek at gcc dot gnu.org 2021-04-22 17:32 ` hewillk at gmail dot com 2021-04-26 14:51 ` mpolacek at gcc dot gnu.org 2021-05-03 16:48 ` cvs-commit at gcc dot gnu.org 2021-05-03 16:49 ` mpolacek at gcc dot gnu.org 2021-11-12 21:23 ` pinskia at gcc dot gnu.org 2022-01-04 2:23 ` pinskia at gcc dot gnu.org 2022-01-04 2:24 ` pinskia at gcc dot gnu.org 2022-01-04 2:26 ` pinskia 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-100055-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).