public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/106334] [13 Regression] lto -g ICE in dwarf2out_register_external_die at dwarf2out.cc:6072
Date: Sun, 31 Jul 2022 07:36:56 +0000 [thread overview]
Message-ID: <bug-106334-4-rrWhXXcWD6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106334-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106334
Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Resolution|FIXED |---
--- Comment #5 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
I'll reopen this bug. I still see the crash in original example. I can make
#comment1 example crash by using `-flto-partition=none` in the link phase:
$ ./result/bin/g++ -O1 -flto -fPIC -g -I. -o eval-cache.o -c eval-cache.cc &&
./result/bin/g++ -O1 -flto -fPIC -g -I. -o eval.o -c eval.cc &&
./result/bin/g++ -O1 -flto -fPIC -g -I. -o libnixexpr.so -shared eval-cache.o
eval.o -flto-partition=none
lto1: internal compiler error: in dwarf2out_register_external_die, at
dwarf2out.cc:6076
0x1dc6714 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char
const*, __va_list_tag (*) [1], diagnostic_t)
???:0
0x1dc7366 internal_error(char const*, ...)
???:0
0x8b7012 fancy_abort(char const*, int, char const*)
???:0
0xa07036 dwarf2out_register_external_die(tree_node*, char const*, unsigned
long)
???:0
0x904efd lto_read_decls(lto_file_decl_data*, void const*,
vec<ld_plugin_symbol_resolution, va_heap, vl_ptr>)
???:0
0x905c6a read_cgraph_and_symbols(unsigned int, char const**)
???:0
0x8edc52 lto_main()
???:0
The compiler should already cpntain the fix:
$ ./result/bin/g++ -v | unnix
Using built-in specs.
COLLECT_GCC=/nix/store/w9kh67lghm1mq5gbcgg06d00d982cyj2-gcc-13.0.0/bin/g++
COLLECT_LTO_WRAPPER=/nix/store/w9kh67lghm1mq5gbcgg06d00d982cyj2-gcc-13.0.0/libexec/gcc/x86_64-unknown-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with:
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20220724 (experimental) (GCC)
next prev parent reply other threads:[~2022-07-31 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 17:34 [Bug lto/106334] New: " slyfox at gcc dot gnu.org
2022-07-17 18:48 ` [Bug lto/106334] " pinskia at gcc dot gnu.org
2022-07-18 8:26 ` rguenth at gcc dot gnu.org
2022-07-18 9:02 ` marxin at gcc dot gnu.org
2022-07-19 9:17 ` cvs-commit at gcc dot gnu.org
2022-07-19 9:18 ` rguenth at gcc dot gnu.org
2022-07-31 7:36 ` slyfox at gcc dot gnu.org [this message]
2022-08-01 8:05 ` rguenth at gcc dot gnu.org
2022-08-02 6:35 ` cvs-commit at gcc dot gnu.org
2022-08-02 6:36 ` rguenth at gcc dot gnu.org
2022-08-08 9:13 ` cvs-commit at gcc dot gnu.org
2022-08-10 14:30 ` cvs-commit at gcc dot gnu.org
2022-10-11 13:04 ` cvs-commit at gcc dot gnu.org
2022-10-14 10:47 ` cvs-commit 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-106334-4-rrWhXXcWD6@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).