This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/54314] [4.8 Regression] undefined references to 'construction vtable for std::ostream-in-std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >'
- From: "jason at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 12 Mar 2013 13:05:52 +0000
- Subject: [Bug libstdc++/54314] [4.8 Regression] undefined references to 'construction vtable for std::ostream-in-std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >'
- Auto-submitted: auto-generated
- References: <bug-54314-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54314
--- Comment #36 from Jason Merrill <jason at gcc dot gnu.org> 2013-03-12 13:05:52 UTC ---
(In reply to comment #35)
> I am still bit confused how keyed construction vtables are supposed to work.
> If I understand it right, and there is no C++ ABI mangling for those, I think
> it makes no sense to export them from the unit they are keyed to, since the
> other units can not refer them anyway.
Right.
> So perhaps the construction vtables should be always comdat hidden?
Hmm? My earlier patch made them hidden, and they were already comdat. Do you
mean something else?