[PATCH] D22034: [MSVC][DLL] use local vftable mangling only exported classes with virtual destructor

[Reid Kleckner via cfe-commits]

rnk added a comment.

In http://reviews.llvm.org/D22034#475540, @DmitryPolukhin wrote:

> Here is B::foo is not exported but required to build vftable for D. Also user may want to explicitly control what should be exported from his library and may decide to remove some functions from exported interface.


Sure, but there are other ways for clients of D to end up referencing the unexported symbol for B::foo, such as devirtualization. Surely you aren't proposing that we power that down just so that we can get the same import/export list as MSVC?


http://reviews.llvm.org/D22034