public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/101905] [9/10/11/12 Regression] Missed debug information for global register variable Date: Wed, 18 Aug 2021 21:10:55 +0000 [thread overview] Message-ID: <bug-101905-4-lVL0w9dC6A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101905-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101905 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- assemble_decl isn't even called for DECL_HARD_REGISTER global vars: if (DECL_HARD_REGISTER (node->decl) || DECL_HAS_VALUE_EXPR_P (node->decl)) continue; if (node->definition) changed |= node->assemble_decl (); else assemble_undefined_decl (node->decl); and even if it would be, it wouldn't get into the spot that calls the debug hook: /* Hard register vars do not need to be output. */ if (DECL_HARD_REGISTER (decl)) return false; ... debug_hooks->late_global_decl (decl); return true; So, either we should make sure that those vars get DW_AT_location already during early debug (IMHO best, as the location should be known then already), or we need to call late_global_decl on those somewhere else.
next prev parent reply other threads:[~2021-08-18 21:10 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-14 2:19 [Bug debug/101905] New: " yuri.karlsbrun at broadcom dot com 2021-08-16 9:03 ` [Bug debug/101905] " rguenth at gcc dot gnu.org 2021-08-16 10:33 ` jakub at gcc dot gnu.org 2021-08-18 20:42 ` yuri.karlsbrun at broadcom dot com 2021-08-18 21:04 ` [Bug debug/101905] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2021-08-18 21:10 ` jakub at gcc dot gnu.org [this message] 2021-08-18 21:34 ` jakub at gcc dot gnu.org 2021-08-19 8:47 ` rguenth at gcc dot gnu.org 2021-08-20 11:33 ` jakub at gcc dot gnu.org 2021-08-20 12:49 ` rguenther at suse dot de 2021-08-23 9:51 ` cvs-commit at gcc dot gnu.org 2021-08-23 9:55 ` cvs-commit at gcc dot gnu.org 2021-08-23 10:05 ` [Bug debug/101905] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:20 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:22 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-101905-4-lVL0w9dC6A@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).