This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Separating type_info classes into separate .o files
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Gabriel Dos Reis <gdr at cs dot tamu dot edu>, libstdc++ <libstdc++ at gcc dot gnu dot org>, "gcc-patches >> GCC Patches" <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 18 Mar 2007 15:37:17 -0700
- Subject: Re: Separating type_info classes into separate .o files
- References: <45FAF6D1.9010305@codesourcery.com> <87mz2d9chg.fsf@soliton.cs.tamu.edu> <45FB7B9D.3050902@codesourcery.com>
Mark Mitchell wrote:
> Gabriel Dos Reis wrote:
>> Mark Mitchell <mark@codesourcery.com> writes:
>>
>> [...]
>>
>> | Do the libstdc++ maintainers have any objections to this change, in
>> | principle?
>>
>> I'm all for it with a caveat:
I've now checked in this patch.
> 2007-03-16 Mark Mitchell <mark@codesourcery.com>
>
> * libsupc++/array_type_info.cc: Likewise.
> * libsupc++/bad_cast.cc: Likewise.
> * libsupc++/bad_typeid.cc: Likewise.
> * libsupc++/class_type_info.cc: Likewise.
> * libsupc++/dyncast.cc: Likewise.
> * libsupc++/enum_type_info.cc: Likewise.
> * libsupc++/function_type_info.cc: Likewise.
> * libsupc++/fundamental_type_info.cc: Likewise.
> * libsupc++/pbase_type_info.cc: Likewise.
> * libsupc++/pmem_type_info.cc: Likewise.
> * libsupc++/pointer_type_info.cc: Likewise.
> * libsupc++/si_class_type_info.cc: Likewise.
> * libsupc++/vmi_class_type_info.cc: Likewise.
> * libsupc++/tinfo.h: Move inline type_info functions here.
> * libsupc++/tinfo.cc: Separate type_info classes into their own
> files.
> * libsupc++/tinfo2.cc: Likewise.
> * Makefile.am (sources): Mention new files.
> * Makefile.in: Regenerated.
Please let me know if there are any problems.
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713