public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94907] New: ICE: Segmentation fault (in check_return_expr) Date: Fri, 01 May 2020 18:08:44 +0000 [thread overview] Message-ID: <bug-94907-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94907 Bug ID: 94907 Summary: ICE: Segmentation fault (in check_return_expr) Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- gcc-10.1.0-RC20200430 ICEs when compiling the following testcase, extracted from test/CXX/class/class.compare/class.compare.default/p4.cpp from the clang 10.0.0 test suite, w/ -std=c++2a: namespace std { struct strong_ordering { }; } struct E; struct D { virtual std::strong_ordering operator<=>(const struct E&) const = 0; }; struct E : D { std::strong_ordering operator<=>(const E&) const override = default; }; % g++-10.1.0 -std=c++2a -c wwmk0dwc.cpp wwmk0dwc.cpp: In member function 'virtual constexpr std::strong_ordering E::operator<=>(const E&) const': wwmk0dwc.cpp:12:24: internal compiler error: Segmentation fault 12 | std::strong_ordering operator<=>(const E&) const override = default; | ^~~~~~~~ 0xfed34f crash_signal /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/toplev.c:328 0xa8008a check_return_expr(tree_node*, bool*) /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/typeck.c:9924 0xa32b5f finish_return_stmt(tree_node*) /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/semantics.c:956 0x964803 build_comparison_op /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/method.c:1445 0x9652d9 synthesize_method(tree_node*) /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/method.c:1550 0x892e02 check_bases_and_members /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/class.c:6002 0x89725b finish_struct_1(tree_node*) /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/class.c:7216 0x898ca4 finish_struct(tree_node*, tree_node*) /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/class.c:7520 0x99abb3 cp_parser_class_specifier_1 /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:23881 0x99cc5b cp_parser_class_specifier /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:24180 0x99cc5b cp_parser_type_specifier /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:17711 0x99dd65 cp_parser_decl_specifier_seq /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:14359 0x99e804 cp_parser_simple_declaration /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:13613 0x9c8ff2 cp_parser_declaration /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:13433 0x9c978f cp_parser_translation_unit /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:4734 0x9c978f c_parse_file() /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/cp/parser.c:43975 0xae268b c_common_parse_file() /var/tmp/portage/sys-devel/gcc-10.1.0_rc20200430/work/gcc-10.1.0-RC-20200430/gcc/c-family/c-opts.c:1190
next reply other threads:[~2020-05-01 18:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-01 18:08 asolokha at gmx dot com [this message] 2020-05-01 18:30 ` [Bug c++/94907] " mpolacek at gcc dot gnu.org 2020-05-04 5:42 ` [Bug c++/94907] ICE: Segmentation fault (in check_return_expr) since r10-8016-gbce54ed494fd0e61 marxin at gcc dot gnu.org 2020-05-04 6:27 ` [Bug c++/94907] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-05-04 13:44 ` jakub at gcc dot gnu.org 2020-05-06 21:37 ` cvs-commit at gcc dot gnu.org 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-05-07 13:28 ` cvs-commit at gcc dot gnu.org 2020-05-07 13:35 ` jakub 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-94907-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).