public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/94459] Missing c++ debug information for 'auto&' return type
Date: Fri, 03 Apr 2020 11:34:21 +0000 [thread overview]
Message-ID: <bug-94459-4-5CJs9rrLnX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94459-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94459
--- Comment #3 from Domani Hannes <ssbssa at yahoo dot de> ---
(In reply to Jakub Jelinek from comment #1)
> Looking through DW_TAG_const_type seems insufficient to me, can't there be
> other qualifications (at least DW_TAG_volatile_type, perhaps in various
> orders)?
> So wouldn't be better a loop as long as die and die->die_tag is one of
> dwarf_qual_info[?].t or DW_TAG_{rvalue_}reference, use die = get_AT_ref
> (die, DW_AT_type); ?
As suggested, I'm now using this:
--- gcc/dwarf2out.c 2020-03-12 12:07:21.000000000 +0100
+++ gcc/dwarf2out.c 2020-04-02 20:10:05.829023900 +0200
@@ -23016,6 +23016,11 @@
if (is_cxx () && debug_info_level > DINFO_LEVEL_TERSE)
{
dw_die_ref die = get_AT_ref (old_die, DW_AT_type);
+ while (die->die_tag == DW_TAG_reference_type
+ || die->die_tag == DW_TAG_rvalue_reference_type
+ || die->die_tag == DW_TAG_const_type
+ || die->die_tag == DW_TAG_volatile_type)
+ die = get_AT_ref (die, DW_AT_type);
if (die == auto_die || die == decltype_auto_die)
add_type_attribute (subr_die, TREE_TYPE (TREE_TYPE (decl)),
TYPE_UNQUALIFIED, false, context_die);
I don't think that restrict/atomic is possible for auto return types, but I may
be wrong about that.
next prev parent reply other threads:[~2020-04-03 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 16:07 [Bug debug/94459] New: " ssbssa at yahoo dot de
2020-04-02 17:36 ` [Bug debug/94459] " jakub at gcc dot gnu.org
2020-04-02 17:41 ` ssbssa at yahoo dot de
2020-04-03 11:34 ` ssbssa at yahoo dot de [this message]
2020-04-03 16:16 ` jakub at gcc dot gnu.org
2020-04-04 12:17 ` ssbssa at yahoo dot de
2020-04-04 22:31 ` cvs-commit at gcc dot gnu.org
2020-04-04 22:35 ` jakub at gcc dot gnu.org
2020-04-07 19:04 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:26 ` 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-94459-4-5CJs9rrLnX@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).