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/107058] [11/12/13 Regression] ICE in dwarf2out_die_ref_for_decl, at dwarf2out.cc:6038 since r11-5003-gd50310408f54e380 Date: Thu, 29 Sep 2022 08:05:37 +0000 [thread overview] Message-ID: <bug-107058-4-y0bPXBNMEA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107058-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107058 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|ipa |debug CC| |rguenth at gcc dot gnu.org --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- #1 0x0000000001223942 in dwarf2out_die_ref_for_decl (decl= <const_decl 0x7ffff669a000 A>, sym=0x7fffffffd170, off=0x7fffffffd168) at /home/rguenther/src/trunk/gcc/dwarf2out.cc:6037 6037 gcc_assert (die->die_tag == DW_TAG_compile_unit (gdb) l 6032 *off = die->die_offset; 6033 while (die->die_parent) 6034 die = die->die_parent; 6035 /* For the containing CU DIE we compute a die_symbol in 6036 compute_comp_unit_symbol. */ 6037 gcc_assert (die->die_tag == DW_TAG_compile_unit 6038 && die->die_id.die_symbol != NULL); 6039 *sym = die->die_id.die_symbol; 6040 return true; 6041 } (gdb) p die->die_tag $1 = DW_TAG_type_unit (gdb) p die->die_id.die_symbol $2 = 0x0 I think -fdebug-types-section isn't handled by early LTO debug I also think we have a duplicate about this. It might also be time to get rid of -fdebug-tyes-section? Nobody uses it. But I'm also not sure why the DIE for a CONST_DECL is inside a type unit? (gdb) p debug_tree (expr) <const_decl 0x7ffff669a000 A type <enumeral_type 0x7ffff6685738 ._anon_0 type <integer_type 0x7ffff66857e0 unsigned int public unsigned SI size <integer_cst 0x7ffff653d1c8 constant 32> unit-size <integer_cst 0x7ffff653d1e0 constant 4> align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 0x7ffff66857e0 precision:8 min <integer_cst 0x7ffff6693a68 0> max <integer_cst 0x7ffff6661ea0 255>> asm_written unsigned type_6 SI size <integer_cst 0x7ffff653d1c8 32> unit-size <integer_cst 0x7ffff653d1e0 4> align:32 warn_if_not_align:0 symtab:-162242480 alias-set -1 canonical-type 0x7ffff6685738 precision:32 min <integer_cst 0x7ffff653d1f8 0> max <integer_cst 0x7ffff653d1b0 4294967295> context <translation_unit_decl 0x7ffff6525168 pr50459.c>> readonly constant used VOID pr50459.c:6:8 align:1 warn_if_not_align:0 context <translation_unit_decl 0x7ffff6525168 pr50459.c> initial <integer_cst 0x7ffff6693ab0 128> chain <type_decl 0x7ffff654abe0 ._anon_0>>
next prev parent reply other threads:[~2022-09-29 8:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-27 16:27 [Bug c++/107058] New: [11/12/13 Regression] ICE in dwarf2out_die_ref_for_decl, at dwarf2out.cc:6038 gscfq@t-online.de 2022-09-27 16:31 ` [Bug debug/107058] " pinskia at gcc dot gnu.org 2022-09-27 16:42 ` [Bug ipa/107058] " mpolacek at gcc dot gnu.org 2022-09-27 17:24 ` [Bug ipa/107058] [11/12/13 Regression] ICE in dwarf2out_die_ref_for_decl, at dwarf2out.cc:6038 since r11-5003-gd50310408f54e380 marxin at gcc dot gnu.org 2022-09-29 8:05 ` rguenth at gcc dot gnu.org [this message] 2023-05-29 10:07 ` [Bug debug/107058] [11/12/13/14 " jakub at gcc dot gnu.org 2024-01-23 8:52 ` [Bug c++/107058] " rguenth at gcc dot gnu.org 2024-01-23 10:15 ` cvs-commit at gcc dot gnu.org 2024-01-23 10:16 ` rguenth at gcc dot gnu.org 2024-03-22 14:02 ` law 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-107058-4-y0bPXBNMEA@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).