Re: [boost] [Serialization] Remaining failures markup

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-09-30 22:35:00

Robert Ramey wrote:
> Aleksey Gurtovoy wrote:

>>Robert,

>>Pending msvc-stlport issue aside, 

> I commented this accordingly.

>>the serialization library reports show
>>quite a few failures with other toolsets, in particular:

>>   cw-9.3
>>   borland-5.6.4
>>   cw-8.3
>>   msvc
>>   vc7

> Metrowerks compilers (cw*) seem to suffer from over-zealous optimization
> that eliminates static variables not referred to explicitly by name.  Other
> compilers do this as well, but I've managed to workaround this in various
> ways.  Cw* is the last hold out on this issue.  I had hoped someone who is
> interested in this can test it might be motivated to look into it but it
> seems that there isn't enough interest.  Unless I hear otherwise, I'll mark
> these tests as "expected".  I would love to see this fixed - but for this
> Metrowerks would have an almost perfect showing.  I do think its very high
> quality product that handles platforms that others don't.  Its pains me that
> the serialization library test don't reflect this.

I'd say mark them as expected for now. I can help in trying to resolve 
the link issues with CW but I don't have much time now. If you can give 
me an easy to reproduce example of the problem, hopefully outside of the 
serialization lib itself, it will make it much easier. I've had this 
problem myself and in one circumstance had to manually add references to 
exception classes in a dummy file+namespace to get their typeinfo linked 
into my DLL.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq