public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/113488] [14 Regression] ICE in add_AT_die_ref with LTO since r14-5546 Date: Fri, 19 Jan 2024 09:43:38 +0000 [thread overview] Message-ID: <bug-113488-4-ZY8LMcihXP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113488-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113488 --- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:62b59bc4f70d02a485c527aa3277f4b4010edb6b commit r14-8281-g62b59bc4f70d02a485c527aa3277f4b4010edb6b Author: Richard Biener <rguenther@suse.de> Date: Fri Jan 19 09:50:43 2024 +0100 debug/113488 - DW_AT_abstract_origin to self The new sanity check avoiding creating of DIE refs to self triggers on the PRs testcase when using -g1 and -ffat-lto-objects as while early DWARF with -g1 doesn't contain any DIEs for LABEL_DECLs later cloning will still mark DECLs as in if they would via dwarf2out_abstract_function calling set_block_origin_self. Instead of messing with the delicate setup of dwarf2out at this stage the following simply rectifies things after the fact during LTO streaming when the decl indicates there's an early DIE but there isn't fixup that indication. PR debug/113488 * lto-streamer-in.cc (lto_read_tree_1): When there isn't an early DIE but there should be, do not pretend there is.
next prev parent reply other threads:[~2024-01-19 9:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 18:14 [Bug lto/113488] New: [14 Regression] ICE in add_AT_die_ref with LTO jakub at gcc dot gnu.org 2024-01-18 18:14 ` [Bug lto/113488] " jakub at gcc dot gnu.org 2024-01-18 18:15 ` jakub at gcc dot gnu.org 2024-01-18 18:28 ` [Bug debug/113488] " jakub at gcc dot gnu.org 2024-01-19 6:22 ` jakub at gcc dot gnu.org 2024-01-19 7:04 ` jakub at gcc dot gnu.org 2024-01-19 7:09 ` [Bug debug/113488] [14 Regression] ICE in add_AT_die_ref with LTO since r14-5546 jakub at gcc dot gnu.org 2024-01-19 7:22 ` rguenth at gcc dot gnu.org 2024-01-19 8:50 ` rguenth at gcc dot gnu.org 2024-01-19 8:52 ` jakub at gcc dot gnu.org 2024-01-19 9:43 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-19 9:48 ` rguenth 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-113488-4-ZY8LMcihXP@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).