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++/99238] [modules] internal compiler error: segmentation fault Date: Tue, 09 Mar 2021 08:19:10 +0000 [thread overview] Message-ID: <bug-99238-4-tahtwHMljd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99238-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99238 --- Comment #3 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> --- About half of sequences of headers producing segmentation fault are stopped on <stop_token>. However there are another variants: ---- g++ -std=c++20 -fmodules-ts -x c++-system-header stdexcept g++ -std=c++20 -fmodules-ts -x c++-system-header locale ---- /usr/local/include/c++/11.0.1/locale: internal compiler error: Segmentation fault 0x10fee8f crash_signal ../../gcc/gcc/toplev.c:327 0x6deab8 trees_out::get_tag(tree_node*) ../../gcc/gcc/cp/module.cc:4783 0x6deab8 trees_out::ref_node(tree_node*) ../../gcc/gcc/cp/module.cc:7090 0x6deab8 trees_out::ref_node(tree_node*) ../../gcc/gcc/cp/module.cc:7073 0xa5dfdc trees_out::tree_node(tree_node*) ../../gcc/gcc/cp/module.cc:8978 0xa5fec9 trees_out::type_node(tree_node*) ../../gcc/gcc/cp/module.cc:8701 0xa5e3da trees_out::tree_node(tree_node*) ../../gcc/gcc/cp/module.cc:9061 0xa5fccc trees_out::type_node(tree_node*) ../../gcc/gcc/cp/module.cc:8619 0xa5e3da trees_out::tree_node(tree_node*) ../../gcc/gcc/cp/module.cc:9061 0xa60104 trees_out::type_node(tree_node*) ../../gcc/gcc/cp/module.cc:8728 0xa5e3da trees_out::tree_node(tree_node*) ../../gcc/gcc/cp/module.cc:9061 0xa5ed0f trees_out::core_vals(tree_node*) ../../gcc/gcc/cp/module.cc:5993 0xa5fbec trees_out::tree_node_vals(tree_node*) ../../gcc/gcc/cp/module.cc:7053 0xa5fbec trees_out::fn_parms_init(tree_node*) ../../gcc/gcc/cp/module.cc:9992 0xa5c4c4 trees_out::decl_value(tree_node*, depset*) ../../gcc/gcc/cp/module.cc:7625 0xa63fd1 depset::hash::find_dependencies(module_state*) ../../gcc/gcc/cp/module.cc:13169 0xa64668 module_state::write(elf_out*, cpp_reader*) ../../gcc/gcc/cp/module.cc:17644 0xa65aff finish_module_processing(cpp_reader*) ../../gcc/gcc/cp/module.cc:19884 0x9f901b 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 20210308 (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.
next prev parent reply other threads:[~2021-03-09 8:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 8:35 [Bug c++/99238] New: " alexander.lelyakin at googlemail dot com 2021-02-28 21:08 ` [Bug c++/99238] " alexander.lelyakin at googlemail dot com 2021-03-09 7:51 ` alexander.lelyakin at googlemail dot com 2021-03-09 8:19 ` alexander.lelyakin at googlemail dot com [this message] 2021-03-12 13:59 ` nathan at gcc dot gnu.org 2021-03-12 18:23 ` cvs-commit at gcc dot gnu.org 2021-03-12 18:23 ` nathan at gcc dot gnu.org 2021-03-13 7:02 ` alexander.lelyakin at googlemail dot com 2021-03-15 12:43 ` nathan 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-99238-4-tahtwHMljd@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).