public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99465] New: Segmentation fault when put lambda into requires clause
Date: Mon, 08 Mar 2021 13:24:22 +0000 [thread overview]
Message-ID: <bug-99465-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99465
Bug ID: 99465
Summary: Segmentation fault when put lambda into requires
clause
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: hewillk at gmail dot com
Target Milestone: ---
The following code will trigger the segmentation fault of gcc-trunk:
template <auto = 0>
auto g() requires ([] { return 0; } ());
int main() { g(); }
godbolt: https://godbolt.org/z/4bsaPd
error message:
<source>: In substitution of 'template<auto <anonymous> > auto g() requires
(<lambda>)() [with auto <anonymous> = 0]':
<source>:4:16: required from here
<source>:2:6: required by the constraints of 'template<auto <anonymous> >
auto g() requires (<lambda>)()'
Segmentation fault
2 | auto g() requires ([] { return 0; } ());
| ~~~~~~~~~~~~~~~~~~^~~
0x1cee989 internal_error(char const*, ...)
???:0
0x7748f3 pp_cxx_parameter_mapping(cxx_pretty_printer*, tree_node*)
???:0
0x7de235 expr_to_string(tree_node*)
???:0
0x1d0a861 pp_format(pretty_printer*, text_info*)
???:0
0x1ced50a diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)
???:0
0x1cee60d error_at(unsigned int, char const*, ...)
???:0
0x73c8ea constraints_satisfied_p(tree_node*, tree_node*)
???:0
0x9510c3 fn_type_unification(tree_node*, tree_node*, tree_node*, tree_node*
const*, unsigned int, tree_node*, unification_kind_t, int, conversion**, bool,
bool)
???:0
0x6db9c2 build_new_function_call(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, int)
???:0
0x97d1ec finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
???:0
0x8dd92d c_parse_file()
???:0
0xa5bd12 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.
next reply other threads:[~2021-03-08 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:24 hewillk at gmail dot com [this message]
2021-03-08 13:35 ` [Bug c++/99465] " hewillk at gmail dot com
2021-03-08 17:21 ` hewillk at gmail dot com
2021-03-10 16:12 ` hewillk at gmail dot com
2021-04-28 20:54 ` mpolacek 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-99465-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: link
Be 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).