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++/99246] [modules] ICE in write_location, at cp/module.cc:15687
Date: Wed, 31 Mar 2021 05:21:03 +0000	[thread overview]
Message-ID: <bug-99246-4-y8Me9jZYO4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99246-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
This report is marked as resolved, but it is stable reproducible all the time.

/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header bit
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header istream
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cmath
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header locale
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header bitset
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header shared_mutex
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header new
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header ciso646
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header memory
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header fstream
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header thread
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header regex
----
In module imported at /usr/local/include/c++/11.0.1/sstream:38:1,
        included from /usr/local/include/c++/11.0.1/regex:46:
/usr/local/include/c++/11.0.1/istream: note: unable to represent further
imported source locations
/usr/local/include/c++/11.0.1/regex: internal compiler error: in
write_location, at cp/module.cc:15593
0x6e02cf module_state::write_location(bytes_out&, unsigned int)
        ../../gcc/gcc/cp/module.cc:15593
0xa60ff3 trees_out::core_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:5900
0xa64464 trees_out::tree_node_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:7050
0xa64464 trees_out::tree_value(tree_node*)
        ../../gcc/gcc/cp/module.cc:8887
0xa604f4 trees_out::tree_node(tree_node*)
        ../../gcc/gcc/cp/module.cc:9085
0xa6484a trees_out::write_var_def(tree_node*)
        ../../gcc/gcc/cp/module.cc:11472
0xa65ae5 module_state::write_cluster(elf_out*, depset**, unsigned int,
depset::hash&, unsigned int*, unsigned int*)
        ../../gcc/gcc/cp/module.cc:14648
0xa6743e module_state::write(elf_out*, cpp_reader*)
        ../../gcc/gcc/cp/module.cc:17720
0xa6801f finish_module_processing(cpp_reader*)
        ../../gcc/gcc/cp/module.cc:19831
0x9fb4cb c_parse_final_cleanups()
        ../../gcc/gcc/cp/decl2.c:5175
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 20210330 (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.

  parent reply	other threads:[~2021-03-31  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  8:49 [Bug c++/99246] New: internal compiler error: " alexander.lelyakin at googlemail dot com
2021-02-26  8:47 ` [Bug c++/99246] [modules] ICE " alexander.lelyakin at googlemail dot com
2021-02-26 12:49 ` nathan at gcc dot gnu.org
2021-03-24 10:04 ` alexander.lelyakin at googlemail dot com
2021-03-31  5:21 ` alexander.lelyakin at googlemail dot com [this message]
2021-04-14 15:19 ` cvs-commit at gcc dot gnu.org
2021-04-15 11:00 ` rsandifo 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-99246-4-y8Me9jZYO4@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).