This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PR22034


> Jan Hubicka <jh@suse.cz> writes:
> 
> [...]
> 
> | The decl is _ZTVZ19GetAssertStackTracevE9StackDump (vtable for
> | GetAssertStackTrace()::StackDump) whose context is the class itself.
> | Why do we emit debug infos for vtables at first place?
> 
> I don't know, but I've certainly done the exercise of debugging
> vtables and type_infos in the not too distant past.  I would think
> theat vtables' context are their classes -- independently of whether
> they are defined at local or nonlocal scopes.

This is precisely what the code did originally and what leads to ICE as
the record_type (class) has no DIE...  I am really quite unsure what is
proper representation here...

Honza
> 
> | I seem to get that probably best thing would be to get the context set
> | to the type but we don't produce dies for types at all, right?
> 
> I'm not an expert in that domain -- I know barely enough to follow the
> discussions on dwarf mailing list.
> 
> -- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]