r188739 - Revert "Revert "Revert "Revert "DebugInfo: Omit debug info for dynamic classes in TUs that do not have the vtable for that class""""

David Blaikie dblaikie at gmail.com
Tue Dec 17 17:38:35 PST 2013


On Tue, Dec 17, 2013 at 5:34 PM, Greg Clayton <gclayton at apple.com> wrote:

> >
> > >
> > > b) -flimit-debug-info is worth, at a guess, somewhere between 1 and
> 5%. This vtable optimization is worth closer to 20%. That's /serious/ bloat
> to consider accepting.
> >
> > I don't consider bloat being something that helps us to completely
> define a type that is going to be use when debugging so we can show the
> entire type and its member variables to the user.
> >
> > How do you know which types are going to be needed by the user? What
> about types that are only declared but not defined in this translation
> unit? ("struct foo; foo *f;")
>
> I will say again what I have said before: if I need to re-create a type
> form DWARF, then I want all the information I need. In order to re-create
> an opaque "struct foo" for a pointer or reference, a declaration is fine.
> If I need to recreate a class, I want all of the base class info.
>

And if someone dereferences that pointer in a debugger expression?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20131217/94037ca5/attachment.html>


More information about the cfe-commits mailing list