public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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 07:22:35 +0000	[thread overview]
Message-ID: <bug-113488-4-Qu5Ljz2SX2@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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look.

(gdb) p debug_dwarf_die (die)
DIE    0: DW_TAG_label (0x7ffff68dc410)
  abbrev id: 0 offset: 0 mark: 0
(gdb) p attr_kind
$2 = DW_AT_abstract_origin

and in gen_label_die we do

  tree origin = decl_ultimate_origin (decl);
  dw_die_ref lbl_die = lookup_decl_die (decl);
  rtx insn;
  char label[MAX_ARTIFICIAL_LABEL_BYTES];

  if (!lbl_die)
    { 
      lbl_die = new_die (DW_TAG_label, context_die, decl);
      equate_decl_number_to_die (decl, lbl_die);

      if (origin != NULL)
        add_abstract_origin_attribute (lbl_die, origin);

but origin == decl here.

(gdb) p decl->decl_common.abstract_origin 
$6 = <label_decl 0x7ffff7fc8e00 no_change>

that's read this way from the LTO data.  A workaround right in dwarf2out
is possible, but I'll see if this self-reference makes sense (and where
it comes from).

  parent reply	other threads:[~2024-01-19  7:22 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 [this message]
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
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-Qu5Ljz2SX2@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).