public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98356] New: [9/10/11 Regression] ICE in cp_parser_dot_deref_incomplete, at cp/parser.c:7899 Date: Thu, 17 Dec 2020 16:52:19 +0000 [thread overview] Message-ID: <bug-98356-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98356 Bug ID: 98356 Summary: [9/10/11 Regression] ICE in cp_parser_dot_deref_incomplete, at cp/parser.c:7899 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Changed between 20190210 (error) and 20190217 (ICE) : (typo ; -> .) $ cat z1.cc template <template <typename> class T> struct S { using A = T<int>; using A::foo; void foo (); void bar () {foo.} }; $ g++-11-20201213 -c z1.cc z1.cc: In member function 'void S<T>::bar()': z1.cc:6:19: internal compiler error: Segmentation fault 6 | void bar () {foo.} | ^ 0xc8f5ff crash_signal ../../gcc/toplev.c:327 0x7d8279 cxx_incomplete_type_diagnostic(unsigned int, tree_node const*, tree_node const*, diagnostic_t) ../../gcc/cp/typeck2.c:373 0x72725e cp_parser_dot_deref_incomplete(tree_node**, cp_expr*, bool*) ../../gcc/cp/parser.c:7899 0x743cb5 cp_parser_postfix_dot_deref_expression ../../gcc/cp/parser.c:7973 0x7414d3 cp_parser_postfix_expression ../../gcc/cp/parser.c:7736 0x751a35 cp_parser_unary_expression ../../gcc/cp/parser.c:8808 0x72b84f cp_parser_cast_expression ../../gcc/cp/parser.c:9712 0x72c082 cp_parser_binary_expression ../../gcc/cp/parser.c:9814 0x72c7e0 cp_parser_assignment_expression ../../gcc/cp/parser.c:10118 0x72d65c cp_parser_expression ../../gcc/cp/parser.c:10288 0x7301e7 cp_parser_expression_statement ../../gcc/cp/parser.c:11955 0x73d44f cp_parser_statement ../../gcc/cp/parser.c:11751 0x73e344 cp_parser_statement_seq_opt ../../gcc/cp/parser.c:12102 0x73e3ff cp_parser_compound_statement ../../gcc/cp/parser.c:12052 0x758ff8 cp_parser_function_body ../../gcc/cp/parser.c:23975 0x758ff8 cp_parser_ctor_initializer_opt_and_function_body ../../gcc/cp/parser.c:24026 0x7594a6 cp_parser_function_definition_after_declarator ../../gcc/cp/parser.c:29916 0x759804 cp_parser_late_parsing_for_member ../../gcc/cp/parser.c:30827 0x73866a cp_parser_class_specifier_1 ../../gcc/cp/parser.c:25088 0x739639 cp_parser_class_specifier ../../gcc/cp/parser.c:25112
next reply other threads:[~2020-12-17 16:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 16:52 gscfq@t-online.de [this message] 2020-12-18 8:48 ` [Bug c++/98356] [9/10/11 Regression] ICE in cp_parser_dot_deref_incomplete, at cp/parser.c:7899 since r9-4841-g2139fd74f31449c0 marxin at gcc dot gnu.org 2020-12-18 12:43 ` nathan at gcc dot gnu.org 2021-01-05 8:34 ` rguenth at gcc dot gnu.org 2021-06-01 8:19 ` [Bug c++/98356] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug c++/98356] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 10:38 ` [Bug c++/98356] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-03-04 23:41 ` mpolacek at gcc dot gnu.org 2024-03-07 11:00 ` cvs-commit at gcc dot gnu.org 2024-03-10 23:16 ` [Bug c++/98356] [11/12/13 " law 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-98356-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).