From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>, Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix dwarf2out ICE with C++17 inline static data members with redundant redeclaration (PR debug/80234)
Date: Thu, 06 Apr 2017 16:51:00 -0000 [thread overview]
Message-ID: <957e5177-7fc5-dac5-848d-b3d3f52d3291@redhat.com> (raw)
In-Reply-To: <20170329194240.GG17461@tucnak>
On 03/29/2017 01:42 PM, Jakub Jelinek wrote:
> Hi!
>
> When a C++17 inline static data member has a redundant out-of-class
> deprecated redeclaration, we can end up with 2 DW_TAG_variable in
> DW_TAG_compile_unit, one DW_AT_declaration and one with DW_AT_specification
> pointing to it (the latter emitted for the redeclaration), before
> gen_member_die can do its job. In there we want to move the declaration
> DIE into the class and have a CU child DW_TAG_variable that has
> DW_AT_specification pointing to it. But in this case we've put
> the DIE with DW_AT_specification into the hash table and gen_member_die
> ICEs in splice_child_die. The following patch handles that case gracefully,
> by moving the DW_AT_declaration DIE into the class instead of trying to
> move the DW_AT_specification one, and by making sure we don't create
> yet another DIE with DW_AT_specification because we already have one.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2017-03-29 Jakub Jelinek <jakub@redhat.com>
>
> PR debug/80234
> * dwarf2out.c (gen_member_die): Handle C++17 inline static data
> members with redundant out-of-class redeclaration.
>
> * g++.dg/debug/dwarf2/pr80234-1.C: New test.
> * g++.dg/debug/dwarf2/pr80234-2.C: New test.
OK.
jeff
prev parent reply other threads:[~2017-04-06 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 19:51 Jakub Jelinek
2017-04-06 16:51 ` Jeff Law [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=957e5177-7fc5-dac5-848d-b3d3f52d3291@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
/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).