[Bug debug/7081] DWARF enhancements for C++

["dberlin at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From dberlin@gcc.gnu.org  2003-06-16 02:23 -------
While i'll fix the first, i don't have the info to fix the second, and until
their is a DWARF3 standard way of describing this, or an extension is proposed,
i plan on closing this bug as fixed, and let him file a second bug.  This should
have been two bugs anyway.

The questions that need to be answered include:
1. What exactly do you want in terms of info about the vtable pointer? The
location? The way to get at each element of the vtable? What?
2. This is not externally visible, or programmer created, info. It's completely
internal to the ABI.  It should *not* be described as a member variable or a
member function of the class.  Thus, it needs a new tag. Otherwise, we'd have to
fudge the name to be something like "vtable", which will cause people unfamiliar
with the internals of C++ to ask us where this "vtable" member is coming from in
their debugger.  In reality, it should be a DW_TAG_vtable or something, that is
a child of the class, and contains attributes like DW_AT_location telling you
the location of the vtable, and probably some child describing how to get each
element as a dwarf3 function.