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++/99915] New: [modules] ICE in write_location
Date: Mon, 05 Apr 2021 11:10:57 +0000	[thread overview]
Message-ID: <bug-99915-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99915
           Summary: [modules] ICE in write_location
           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: ---

This ICE is very similar to 99246, but it is closed as fixed.
So I assume that it is a new bug with similar symptoms.

/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:15607
0x6de279 module_state::write_location(bytes_out&, unsigned int)
        ../../gcc/gcc/cp/module.cc:15607
0xa67153 trees_out::core_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:5904
0xa6a5c4 trees_out::tree_node_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:7054
0xa6a5c4 trees_out::tree_value(tree_node*)
        ../../gcc/gcc/cp/module.cc:8890
0xa66654 trees_out::tree_node(tree_node*)
        ../../gcc/gcc/cp/module.cc:9088
0xa6a9aa trees_out::write_var_def(tree_node*)
        ../../gcc/gcc/cp/module.cc:11475
0xa6bc45 module_state::write_cluster(elf_out*, depset**, unsigned int,
depset::hash&, unsigned int*, unsigned int*)
        ../../gcc/gcc/cp/module.cc:14662
0xa6d5ce module_state::write(elf_out*, cpp_reader*)
        ../../gcc/gcc/cp/module.cc:17734
0xa6e338 finish_module_processing(cpp_reader*)
        ../../gcc/gcc/cp/module.cc:19845
0xa014cb 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 20210405 (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-04-05 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 11:10 alexander.lelyakin at googlemail dot com [this message]
2021-04-09 16:31 ` [Bug c++/99915] " alexander.lelyakin at googlemail dot com
2022-01-01  4:11 ` pinskia at gcc dot gnu.org
2022-01-01  4:23 ` pinskia at gcc dot gnu.org
2022-01-01  4:24 ` 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-99915-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).