[Bug default/28584] New: abidw doesn't get Clang DWARF type information for certain symbols

["gprocida at google dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28584

            Bug ID: 28584
           Summary: abidw doesn't get Clang DWARF type information for
                    certain symbols
           Product: libabigail
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: gprocida at google dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

Created attachment 13776
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13776&action=edit
test case

Consider these two code fragments.

namespace N {                                                                   
struct S { static int D; };                                                     
}                                                                               
int N::S::D = 17;                                                               


namespace N {                                                                   
struct S { static int D; };                                                     
int S::D = 17;                                                                  
}                                                                               

Looking at the DWARF, in all cases the variable declaration linked to the
symbol is a separate entity (with just a linkage name) from the member within
the struct.

While GCC produces essentially identical DWARF for both fragments above, Clang
does something different for the second case. For GCC, this entity exists
outside the namespace scope. For Clang it exists in the scope it appeared in
the file (global and namespace N scope, for the two examples, respectively).

abidw doesn't appear to handle Clang's inner-scoped DW_TAG_variables. I express
no opinion as to which is wrong. :-)

I've attached a full test case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.