On 20 June 2013 22:17, David Blaikie <[email protected]> wrote: > I've talked to Richard Smith about a more > principled approach where we could add a new ASTConsumer callback that > fires whenever Sema discovers that a complete type is required > (Sema::RequireCompleteType is called for the first time on a type). >
I know it sounds wrong, but couldn't you add the info on all declaration and let DCE remove it if not needed? Ie. I'm actually surprised that it doesn't... Does it? So next time we go > to retrieve it, even if this time we say we need a definition, we > retrieve the cached typedef type and use that - never pushing further > into it to emit the definition of the nested type. > Oh, I remember vaguely having a similar bug on our front end, because you don't want to create a declaration for both types if they're related and end up with different metadata for each path. I don't remember how I solved it, but it was definitely the wrong way, because Dwarf was, by far, the worst part of our bridge. ;) cheers, --renato
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
