Separating type_info classes into separate .o files

[Mark Mitchell]

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:
> 
>    A documentation of how the "new" files make up the old files.

I don't understand what you're requesting.  I would just take tinfo2.cc
and split it into array_type_info.cc, si_class_type_info.cc,
fundamental_typeinfo.cc, etc.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713