public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ryan.burn at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99543] New: ICE module compilation ../../gcc/toplev.c:327 Date: Thu, 11 Mar 2021 06:18:42 +0000 [thread overview] Message-ID: <bug-99543-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99543 Bug ID: 99543 Summary: ICE module compilation ../../gcc/toplev.c:327 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ryan.burn at gmail dot com Target Milestone: --- Here is the stacktrace. It happened when I tried to compile a header module that imported another header module: // a.h import <iostream>; SUBCOMMAND: # //example/header-module:a_hdr [action 'Action example/header-module/a.h.gcm', configuration: 86d23d2b5aedbeecfc6e6954ea9486ec39e9e40bcbc4b17cec46a06eed198d11, execution platform: @local_config_platform//:host] (cd /root/.cache/bazel/_bazel_root/f8087e59fd95af1ae29e8fcb7ff1a3dc/execroot/com_github_rnburn_bazel_cpp20_modules && \ exec env - \ bazel-out/k8-opt-exec-2B5CBBC6/bin/util/process_wrapper/process_wrapper -- /usr/local/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -Ibazel-out/k8-fastbuild/bin/example/header-module/system/iostream-include -x c++-header -fmodules-ts '-std=c++20' -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c example/header-module/a.h '-fmodule-mapper=bazel-out/k8-fastbuild/bin/example/header-module/a_hdr-module-map' -iquote .) INFO: From Action example/header-module/a.h.gcm: example/header-module/a.h: internal compiler error: Segmentation fault 0x10a9ccf crash_signal ../../gcc/toplev.c:327 0x1c671d6 get_location_from_adhoc_loc(line_maps const*, unsigned int) ../../libcpp/line-map.c:257 0x9ff6dd module_state::write_location(bytes_out&, unsigned int) ../../gcc/cp/module.cc:15569 0xa01faf module_state::write_define(bytes_out&, cpp_macro const*, bool) ../../gcc/cp/module.cc:16337 0xa0340a module_state::write_macros(elf_out*, cpp_reader*, unsigned int*) ../../gcc/cp/module.cc:16839 0xa16218 module_state::write(elf_out*, cpp_reader*) ../../gcc/cp/module.cc:17713 0xa168f5 finish_module_processing(cpp_reader*) ../../gcc/cp/module.cc:19728 0x9aaa8b c_parse_final_cleanups() ../../gcc/cp/decl2.c:5170 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. gcc version root@748001480fc4:/src# g++ --version g++ (GCC) 11.0.0 20201218 (experimental) Copyright (C) 2020 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 reply other threads:[~2021-03-11 6:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-11 6:18 ryan.burn at gmail dot com [this message] 2021-03-11 8:45 ` [Bug c++/99543] " rguenth at gcc dot gnu.org 2021-03-12 23:18 ` ryan.burn at gmail dot com 2021-03-12 23:18 ` ryan.burn at gmail 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-99543-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: 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).