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++/99734] [modules] ICE in most_specialized_instantiation
Date: Tue, 23 Mar 2021 17:09:56 +0000	[thread overview]
Message-ID: <bug-99734-4-lQ4iu3sM2B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99734-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header stdexcept
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header filesystem
----
In file included from /usr/local/include/c++/11.0.1/bits/locale_classes.h:857,
                 from /usr/local/include/c++/11.0.1/locale:39,
                 from /usr/local/include/c++/11.0.1/bits/fs_path.h:37,
                 from /usr/local/include/c++/11.0.1/filesystem:45:
/usr/local/include/c++/11.0.1/bits/locale_classes.tcc:275:44: internal compiler
error: in most_specialized_instantiation, at cp/pt.c:24830
  275 |     use_facet<collate<char> >(const locale&);
      |                                            ^
0x725070 most_specialized_instantiation(tree_node*)
        ../../gcc/gcc/cp/pt.c:24830
0xb2e1e9 determine_specialization
        ../../gcc/gcc/cp/pt.c:2457
0xb3418c determine_specialization
        ../../gcc/gcc/cp/pt.c:2156
0xb3418c check_explicit_specialization(tree_node*, tree_node*, int, int,
tree_node*)
        ../../gcc/gcc/cp/pt.c:3121
0x9d481e grokfndecl
        ../../gcc/gcc/cp/decl.c:10064
0x9db1f3 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*,
decl_context, int, tree_node**)
        ../../gcc/gcc/cp/decl.c:13910
0xac82c1 cp_parser_explicit_instantiation
        ../../gcc/gcc/cp/parser.c:18240
0xad8840 cp_parser_declaration
        ../../gcc/gcc/cp/parser.c:14096
0xad80e9 cp_parser_toplevel_declaration
        ../../gcc/gcc/cp/parser.c:14159
0xad80e9 cp_parser_declaration_seq_opt
        ../../gcc/gcc/cp/parser.c:13947
0xad8582 cp_parser_namespace_body
        ../../gcc/gcc/cp/parser.c:20447
0xad8582 cp_parser_namespace_definition
        ../../gcc/gcc/cp/parser.c:20425
0xad8cd8 cp_parser_declaration
        ../../gcc/gcc/cp/parser.c:14110
0xad952c cp_parser_toplevel_declaration
        ../../gcc/gcc/cp/parser.c:14159
0xad952c cp_parser_translation_unit
        ../../gcc/gcc/cp/parser.c:4942
0xad952c c_parse_file()
        ../../gcc/gcc/cp/parser.c:45250
0xbfd51d c_common_parse_file()
        ../../gcc/gcc/c-family/c-opts.c:1218
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 20210323 (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-03-23 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 17:08 [Bug c++/99734] New: " alexander.lelyakin at googlemail dot com
2021-03-23 17:09 ` alexander.lelyakin at googlemail dot com [this message]
2021-03-25 11:51 ` [Bug c++/99734] " alexander.lelyakin at googlemail dot com
2021-03-30  1:22 ` mpolacek at gcc dot gnu.org
2022-01-04  2:22 ` 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-99734-4-lQ4iu3sM2B@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).