Re: [Boost-users] [serialization] Out of memory with Borland C++Builder 60

From: Robert Ramey (ramey_at_[hidden])
Date: 2006-06-30 14:47:31

One thing that might or might help is using the approach
illustrated in the example demo_pimpl.  The permits
serialization for each combination of data type and
archive type to be compiled separately.  This might
keep things small enough to avoid the compiler's
problems.

Robert Ramey

Federico Feller wrote:
> Russell, thanks for your answer. I've tried removing
> the template specifications, but it didn't solve the
> problem. Unfortunally I had to stop using the
> serialization library and try something else.
>
> Cheers
>
> Federico
>
> --- Russell Hind <rh_gmane_at_[hidden]> wrote:
>
>> Federico Feller wrote:
>>>
>>> After doing that, I tried to compile the code and
>> got
>>> the following error from the compiler:
>>>
>>> [C++ Fatal Error] if.hpp(72): F1008 Out of memory
>>>
>>
>> I have lots of problems using serialization under
>> BCB6.  Only with our
>> large data structures of many nested classes.  A lot
>> of our issues have
>> to do with inline expansions in release builds so
>> disabling these helps,
>> but I have still got to the stage where we get
>> problems even in debug
>> builds.
>>
>> We get internal compiler errors.  My guess is that
>> the amount of
>> template code generated is just too much for the
>> compiler, as simple,
>> small, classes serialize fine, but bigger ones can
>> be pushed over the
>> edge by adding one more member to the list.
>>
>> My best guess for us at a solution is to stop
>> functions being template
>> based.  I.e. if you know your class gets serialized
>> to binary archives
>> only, create non-template functions that don't have
>> to have
>> implementations in the header, and split them
>> accross translation units
>> such as
>>
>> void serialize_part1(binary_oarchive& boa);
>> void serialize_part2(binary_oarchive& boa);
>>
>> I haven't tried this yet, but it is the only way I
>> can think of to
>> reduce the load on the compiler.  The serialization
>> library does stress
>> the compiler quite badly because of the amount of
>> inline-able and
>> template based code.
>>
>> Cheers
>>
>> Russell
>>
>> _______________________________________________
>> Boost-users mailing list
>> Boost-users_at_[hidden]
>>
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com