public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105803] [13 regression] ICE at gcc/cp/pt.cc:27737 after r13-860-gff91735a5b861d Date: Wed, 01 Jun 2022 19:09:34 +0000 [thread overview] Message-ID: <bug-105803-4-76aG2Hr8f8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105803-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105803 --- Comment #4 from seurer at gcc dot gnu.org --- Yes it is: seurer@muskie:~/gcc/cpu2017/benchspec/CPU/510.parest_r/build/build_peak_none.0002$ whichgcc Now at commit ff91735a5b861dd6eaf2c1e511f26a9255898e7d, r13-860-gff91735a5b861d seurer@muskie:~/gcc/cpu2017/benchspec/CPU/510.parest_r/build/build_peak_none.0002$ cat test.cc #include <vector> #include <memory> class SparsityPattern { public: }; template <class SparsityPatternBase> class BlockSparsityPatternBase// : public Subscriptor { }; class BlockSparsityPattern : public BlockSparsityPatternBase<SparsityPattern> { }; class MGTransferBlockBase { public: std::vector<std::shared_ptr<BlockSparsityPattern> > prolongation_sparsities; template <int dim, int spacedim> void build_matrices (); }; template <int dim, int spacedim> void MGTransferBlockBase::build_matrices () { prolongation_sparsities.push_back (std::shared_ptr<BlockSparsityPattern> (new BlockSparsityPattern)); } seurer@muskie:~/gcc/cpu2017/benchspec/CPU/510.parest_r/build/build_peak_none.0002$ /home/seurer/gcc/git/install/gcc-test/bin/g++ -c test.cc test.cc: In member function 'void MGTransferBlockBase::build_matrices()': test.cc:31:37: internal compiler error: in type_dependent_expression_p, at cp/pt.cc:27737 31 | prolongation_sparsities.push_back (std::shared_ptr<BlockSparsityPattern> (new BlockSparsityPattern)); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0x1063cb33 type_dependent_expression_p(tree_node*) /home/seurer/gcc/git/gcc-test/gcc/cp/pt.cc:27737 0x1063d6f3 value_dependent_expression_p(tree_node*) /home/seurer/gcc/git/gcc-test/gcc/cp/pt.cc:27465 0x1063df77 value_dependent_expression_p(tree_node*) /home/seurer/gcc/git/gcc-test/gcc/cp/pt.cc:27707 0x106447cf any_value_dependent_elements_p(tree_node const*) /home/seurer/gcc/git/gcc-test/gcc/cp/pt.cc:28184 0x103a7257 is_nondependent_constant_expression(tree_node*) /home/seurer/gcc/git/gcc-test/gcc/cp/constexpr.cc:9673 0x103a7913 fold_non_dependent_expr_template /home/seurer/gcc/git/gcc-test/gcc/cp/constexpr.cc:8172 0x10636ea3 build_non_dependent_expr(tree_node*) /home/seurer/gcc/git/gcc-test/gcc/cp/pt.cc:28647 0x106379a3 make_args_non_dependent(vec<tree_node*, va_gc, vl_embed>*) /home/seurer/gcc/git/gcc-test/gcc/cp/pt.cc:28729 0x1033ea53 build_new_method_call(tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>**, tree_node*, int, tree_node**, int) /home/seurer/gcc/git/gcc-test/gcc/cp/call.cc:10939 0x105d91e7 cp_parser_postfix_expression /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:7856 0x105fddd3 cp_parser_unary_expression /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:9037 0x105b0307 cp_parser_cast_expression /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:9941 0x105b0e83 cp_parser_binary_expression /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:10043 0x105b1aff cp_parser_assignment_expression /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:10347 0x105b5d33 cp_parser_expression /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:10517 0x105ba46b cp_parser_expression_statement /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:12734 0x105d22ff cp_parser_statement /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:12526 0x105d3803 cp_parser_statement_seq_opt /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:12883 0x105d3957 cp_parser_compound_statement /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:12835 0x1060f613 cp_parser_function_body /home/seurer/gcc/git/gcc-test/gcc/cp/parser.cc:25186
next prev parent reply other threads:[~2022-06-01 19:09 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-01 14:33 [Bug c++/105803] New: " seurer at gcc dot gnu.org 2022-06-01 14:36 ` [Bug c++/105803] " mpolacek at gcc dot gnu.org 2022-06-01 16:46 ` seurer at gcc dot gnu.org 2022-06-01 17:34 ` mpolacek at gcc dot gnu.org 2022-06-01 19:09 ` seurer at gcc dot gnu.org [this message] 2022-06-01 19:11 ` seurer at gcc dot gnu.org 2022-06-01 19:46 ` mpolacek at gcc dot gnu.org 2022-06-01 19:50 ` mpolacek at gcc dot gnu.org 2022-06-01 20:11 ` mpolacek at gcc dot gnu.org 2022-06-02 2:33 ` crazylht at gmail dot com 2022-06-02 2:34 ` crazylht at gmail dot com 2022-06-02 20:01 ` cvs-commit at gcc dot gnu.org 2022-06-02 20:02 ` mpolacek 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-105803-4-76aG2Hr8f8@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).