public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Mon, 23 Aug 2021 09:51:28 +0000	[thread overview]
Message-ID: <bug-101905-4-ZlPtWwazdE@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 #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:b284053bb75661fc1bf13c275f3ba5364bb17608

commit r12-3069-gb284053bb75661fc1bf13c275f3ba5364bb17608
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Aug 23 11:50:14 2021 +0200

    dwarf2out: Emit DW_AT_location for global register vars during early dwarf
[PR101905]

    The following patch emits DW_AT_location for global register variables
    already during early dwarf, since usually late_global_decl hook isn't even
    called for those, as nothing needs to be emitted for them.

    2021-08-23  Jakub Jelinek  <jakub@redhat.com>

            PR debug/101905
            * dwarf2out.c (gen_variable_die): Add DW_AT_location for global
            register variables already during early_dwarf if possible.

            * gcc.dg/guality/pr101905.c: New test.

  parent reply	other threads:[~2021-08-23  9:51 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
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 [this message]
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-ZlPtWwazdE@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).