[LLVMdev] [cfe-dev] anchoring explicit template instantiations

Ted Kremenek kremenek at apple.com
Mon Dec 19 20:39:12 PST 2011

On Dec 19, 2011, at 5:40 PM, Chris Lattner wrote:

>> (also, I implemented this by adding private anchors, like my original
>> version - this does actually have a difference at runtime, of course -
>> since now each of these types has another entry in their vtable.
> I think that's a perfectly fine cost :)

Why is this acceptable?  Can't we just move more virtual methods out-of-line?  If we had a warning to find which classes we need to fix, why not just enforce that warning going forward as part of building the codebase once all of the offending classes are fixed?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111219/709b8f8d/attachment.html>

More information about the llvm-dev mailing list