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/94450] lto abstract variable emitted as concrete decl Date: Thu, 02 Apr 2020 10:22:49 +0000 [thread overview] Message-ID: <bug-94450-4-veAuADUyIi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94450 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Richard Biener from comment #2) > So the current situation is similar to that of Modifying the testcase to C99 inline int foo(int i) { static int j; j = i + 1; return j; } int bar(int i) { return foo(i); } int baz(int i) { return foo(i); } extern int foo(int i); [...] > Note we're not emitting a concrete instance of the function which would > contain the "main" instance of 'j'. Not sure what the DWARF for a > standalone concrete instantiation of 'j' would look like. The concrete instance is emitted: <1><57>: Abbrev Number: 6 (DW_TAG_subprogram) <58> DW_AT_abstract_origin: <0x2d> <5c> DW_AT_low_pc : 0x0 <64> DW_AT_high_pc : 0xa <6c> DW_AT_frame_base : 1 byte block: 9c (DW_OP_call_frame_cfa) <6e> DW_AT_GNU_all_call_sites: 1 <6e> DW_AT_sibling : <0x89> <2><72>: Abbrev Number: 7 (DW_TAG_formal_parameter) <73> DW_AT_abstract_origin: <0x3d> <77> DW_AT_location : 1 byte block: 55 (DW_OP_reg5 (rdi)) <2><79>: Abbrev Number: 8 (DW_TAG_variable) <7a> DW_AT_abstract_origin: <0x46> <7e> DW_AT_location : 9 byte block: 3 0 0 0 0 0 0 0 0 (DW_OP_addr: 0) so here's another copy of the variable. I guess for function local variables gdb isn't fooled to think it has two copies? And the bogus copy is not because of the abstract origin link but because of the unit import but could be brought in by other means of making gdb read the DWARF of it?
next prev parent reply other threads:[~2020-04-02 10:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-01 21:51 [Bug debug/94450] New: " vries at gcc dot gnu.org 2020-04-02 8:07 ` [Bug debug/94450] " rguenth at gcc dot gnu.org 2020-04-02 10:17 ` rguenth at gcc dot gnu.org 2020-04-02 10:22 ` rguenth at gcc dot gnu.org [this message] 2020-04-02 10:25 ` rguenth at gcc dot gnu.org 2020-04-02 12:29 ` vries at gcc dot gnu.org 2020-04-02 14:48 ` cvs-commit at gcc dot gnu.org 2020-04-02 14:48 ` rguenth at gcc dot gnu.org 2020-04-03 10:26 ` vries at gcc dot gnu.org 2020-04-03 11:10 ` rguenther at suse dot de 2020-04-03 12:52 ` vries at gcc dot gnu.org 2020-04-03 13:03 ` rguenther at suse dot de 2020-04-03 13:23 ` vries at gcc dot gnu.org 2020-04-03 16:43 ` vries 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-94450-4-veAuADUyIi@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).