public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander.lelyakin at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99283] New: [modules] ICE in assert_definition, at cp/module.cc:4608
Date: Fri, 26 Feb 2021 08:51:44 +0000	[thread overview]
Message-ID: <bug-99283-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99283

            Bug ID: 99283
           Summary: [modules] ICE in assert_definition, at
                    cp/module.cc:4608
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: alexander.lelyakin at googlemail dot com
  Target Milestone: ---

g++ -std=c++20 -fmodules-ts -x c++-system-header stdexcept
g++ -std=c++20 -fmodules-ts -x c++-system-header scoped_allocator
g++ -std=c++20 -fmodules-ts -x c++-system-header exception
g++ -std=c++20 -fmodules-ts -x c++-system-header cerrno
g++ -std=c++20 -fmodules-ts -x c++-system-header numbers
g++ -std=c++20 -fmodules-ts -x c++-system-header sstream
----
In file included from /usr/local/include/c++/11.0.1/bits/ios_base.h:46,
                 from /usr/local/include/c++/11.0.1/ios:42,
                 from /usr/local/include/c++/11.0.1/istream:38,
                 from /usr/local/include/c++/11.0.1/sstream:38:
/usr/local/include/c++/11.0.1/system_error:68:14: internal compiler error: in
assert_definition, at cp/module.cc:4608
   68 |     : public true_type { };
      |              ^~~~~~~~~
0x6df83a trees_in::assert_definition(tree_node*, bool)
        ../../gcc/gcc/cp/module.cc:4608
0xa591e0 trees_in::odr_duplicate(tree_node*, bool)
        ../../gcc/gcc/cp/module.cc:11489
0xa69e8f trees_in::read_function_def(tree_node*, tree_node*)
        ../../gcc/gcc/cp/module.cc:11569
0xa6c2a9 module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14957
0xa6c96d module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18148
0xa6ca2f module_state::lazy_load(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18800
0xa66c70 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9762
0xa65d79 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9301
0xa67807 trees_in::core_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:6651
0xa63ed7 trees_in::tree_node_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:7175
0xa63ed7 trees_in::decl_value()
        ../../gcc/gcc/cp/module.cc:8070
0xa65e07 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9251
0xa6c5c3 module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14948
0xa6c96d module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18148
0xa6d008 lazy_load_binding(unsigned int, tree_node*, tree_node*, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18833
0xa7ce8e name_lookup::search_namespace_only(tree_node*)
        ../../gcc/gcc/cp/name-lookup.c:924
0xa7e5eb name_lookup::search_unqualified(tree_node*, cp_binding_level*)
        ../../gcc/gcc/cp/name-lookup.c:1155
0xa813e4 lookup_name_1
        ../../gcc/gcc/cp/name-lookup.c:7868
0xa815aa lookup_name(tree_node*, LOOK_where, LOOK_want)
        ../../gcc/gcc/cp/name-lookup.c:7888
0xa902c2 lookup_name(tree_node*, LOOK_want)
        ../../gcc/gcc/cp/name-lookup.h:412
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.
----
g++ (GCC) 11.0.1 20210225 (experimental)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

----

             reply	other threads:[~2021-02-26  8:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26  8:51 alexander.lelyakin at googlemail dot com [this message]
2021-03-05 21:06 ` [Bug c++/99283] " nathan at gcc dot gnu.org
2021-03-05 21:44 ` alexander.lelyakin at googlemail dot com
2021-03-05 23:09 ` alexander.lelyakin at googlemail dot com
2021-03-06  7:45 ` alexander.lelyakin at googlemail dot com
2021-03-13  7:07 ` alexander.lelyakin at googlemail dot com
2021-03-23 19:29 ` cvs-commit at gcc dot gnu.org
2021-03-23 19:30 ` nathan at gcc dot gnu.org
2021-03-24  6:41 ` alexander.lelyakin at googlemail dot com
2021-03-24 19:46 ` alexander.lelyakin at googlemail dot com
2021-03-26 19:08 ` cvs-commit at gcc dot gnu.org
2021-03-26 19:09 ` nathan at gcc dot gnu.org
2021-03-27  6:27 ` alexander.lelyakin at googlemail dot com
2021-03-27 18:29 ` alexander.lelyakin at googlemail dot com
2021-03-30 16:52 ` cvs-commit at gcc dot gnu.org
2021-03-30 16:53 ` nathan at gcc dot gnu.org
2021-03-30 20:01 ` alexander.lelyakin at googlemail dot com
2021-04-01 12:37 ` cvs-commit at gcc dot gnu.org
2021-04-01 12:38 ` nathan at gcc dot gnu.org
2021-04-01 12:39 ` nathan at gcc dot gnu.org
2021-04-01 12:56 ` alexander.lelyakin at googlemail dot com
2021-04-01 13:40 ` nathan at gcc dot gnu.org
2021-04-01 13:43 ` alexander.lelyakin at googlemail dot com
2021-04-02 16:09 ` nathan at gcc dot gnu.org
2021-04-02 17:16 ` alexander.lelyakin at googlemail dot com

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-99283-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).