This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Separating type_info classes into separate .o files
- From: Mark Mitchell <mark at codesourcery dot com>
- To: libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Fri, 16 Mar 2007 12:58:09 -0700
- Subject: Separating type_info classes into separate .o files
The tinfo2.cc file in libsupc++ contains implementations of all the C++
ABI type_info routines. For example, that file contains
__pbase_type_info::__do_catch, and
__function_type_info::~__function_type_info. The virtual tables (and
type_info objects!) for all of the type_info classes are also defined in
tinfo2.cc; that's the reason for the destructor definitions.
Many programs need some of these classes, but not others. In
particular, things like __array_type_info and __function_type_info are
rarely needed. On embedded systems, this is a bit of library bloat, and
we can easily eliminate it, by separating tinfo2.cc into a separate file
per type_info class.
Do the libstdc++ maintainers have any objections to this change, in
principle?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713