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/110439] Missing DW_TAG_typedef for variable with attribute of typedef'd type Date: Wed, 28 Jun 2023 07:54:23 +0000 [thread overview] Message-ID: <bug-110439-4-CqsUw3d3ti@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110439-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110439 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2023-06-28 Ever confirmed|0 |1 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- it works fine with foo const attr_foo; where we generate <1><1e>: Abbrev Number: 3 (DW_TAG_typedef) <1f> DW_AT_name : foo <23> DW_AT_decl_file : 1 <24> DW_AT_decl_line : 1 <25> DW_AT_decl_column : 13 <26> DW_AT_type : <0x2f> <1><2a>: Abbrev Number: 4 (DW_TAG_const_type) <2b> DW_AT_type : <0x1e> <1><36>: Abbrev Number: 1 (DW_TAG_variable) <37> DW_AT_name : (indirect string, offset: 0xa): attr_foo <3b> DW_AT_decl_file : 1 <3b> DW_AT_decl_line : 2 <3c> DW_AT_decl_column : 11 <3d> DW_AT_type : <0x2a> <41> DW_AT_external : 1 <41> DW_AT_location : 9 byte block: 3 0 0 0 0 0 0 0 0 (DW_OP_addr: 0) to GCC the attribute generates a similar type variant but there's no way to emit the "qualification" in dwarf but it looks like for consistency we should then fall back to the typedef DIE, not the base type DIE. Confirmed.
prev parent reply other threads:[~2023-06-28 7:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-27 18:32 [Bug debug/110439] New: " david.faust at oracle dot com 2023-06-27 18:39 ` [Bug debug/110439] " pinskia at gcc dot gnu.org 2023-06-27 18:45 ` david.faust at oracle dot com 2023-06-28 7:54 ` rguenth at gcc dot gnu.org [this message]
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-110439-4-CqsUw3d3ti@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).