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/51950] [4.6/4.7 Regression] fdebug-types-section regression for member pointers
Date: Wed, 25 Jan 2012 18:40:00 -0000	[thread overview]
Message-ID: <bug-51950-4-NNjlsWhpZR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51950-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51950

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-01-25
         AssignedTo|unassigned at gcc dot       |jakub at gcc dot gnu.org
                   |gnu.org                     |
     Ever Confirmed|0                           |1

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-25 17:41:58 UTC ---
Created attachment 26465
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26465
gcc47-pr51950.patch

Untested fix.

This "regressed" with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162691
which just made a cloning bug no longer latent, because DW_AT_object_pointer
the patch added is a reference to one of its children.  The problem is that we
were using clone_tree to clone all the children (in this case of
DW_TAG_subroutine_type), but clone_tree didn't enter all the children
(DW_TAG_formal_parameter in particular) into the hash table.  So we ended up
with a clone DW_TAG_subroutine_type with a single cloned
DW_TAG_formal_parameter.  Next clone_decls_walk attempted to adjust the
references in the attributes (DW_AT_object_pointer), but nothing was in the
hash table, so it created another DW_TAG_formal_parameter clone, and when
adding also its ancestor tree the DW_TAG_subroutine_type has been found in the
hash table and so this second DW_TAG_formal_parameter has been added as another
child.


  parent reply	other threads:[~2012-01-25 17:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 19:37 [Bug debug/51950] New: [4.6 " jan.kratochvil at redhat dot com
2012-01-23 10:51 ` [Bug debug/51950] [4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-23 11:29 ` jan.kratochvil at redhat dot com
2012-01-25 18:40 ` jakub at gcc dot gnu.org [this message]
2012-02-07 15:42 ` rguenth at gcc dot gnu.org
2012-02-14 19:42 ` jakub at gcc dot gnu.org
2012-02-14 19:50 ` [Bug debug/51950] [4.6 " jakub at gcc dot gnu.org
2012-02-14 23:35 ` jakub at gcc dot gnu.org
2012-02-14 23:47 ` 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-51950-4-NNjlsWhpZR@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).