On Thu, Nov 21, 2013 at 08:46:12PM -0500, Howard Hinnant wrote: > If I'm remembering correctly, it goes something like: If something is > marked __always_inline__, it doesn't get outlined when the templated > is explicitly instantiated into a source (which I believe is correct > behavior). However when the client needs an __always_inline__ and the > type is marked extern template, the client assumes it can find the > symbol outlined elsewhere (which I believe is incorrect behavior).
Correct, the backend problem here is that the destructor ends up with available_externally and always_inline. The combination is logically consistent, but changing the interpretation of that is something I'd like to defer for now. Joerg _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
