Boost C++ Libraries: Ticket #7010: A few 32/64 bit warning fixes https://svn.boost.org/trac10/ticket/7010 <p> if of any interest. Mainly (only?) <a class="missing wiki">SunStudio</a>, if memory serves. </p> <p> Regards </p> <p> Luke Elliott. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/7010 Trac 1.4.3 Luke Elliott <lukester_null@…> Thu, 21 Jun 2012 15:50:16 GMT attachment set https://svn.boost.org/trac10/ticket/7010 https://svn.boost.org/trac10/ticket/7010 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">ser.patch</span> </li> </ul> Ticket lukester_null@… Wed, 27 Jun 2012 10:08:02 GMT component changed; owner set https://svn.boost.org/trac10/ticket/7010#comment:1 https://svn.boost.org/trac10/ticket/7010#comment:1 <ul> <li><strong>owner</strong> set to <span class="trac-author">Robert Ramey</span> </li> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">serialization</span> </li> </ul> Ticket anonymous Thu, 12 Jul 2012 16:10:22 GMT <link>https://svn.boost.org/trac10/ticket/7010#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/7010#comment:2</guid> <description> <p> hmmm - the sun compiler fails the trunk test suite. Since you're using this and the serialization library, maybe you could run the serialization library tests on your system and track down the cause of these failures. I suspect it's just a standard io library quirk but there's nothing I can do about it on my own. I believe that a little sleuthing would be rewarded with a couple of changes which would result if the sun compiler passing (almost) all tests. </p> <p> Robert Ramey </p> </description> <category>Ticket</category> </item> <item> <author>lukester_null@…</author> <pubDate>Thu, 12 Jul 2012 16:50:01 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/7010#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/7010#comment:3</guid> <description> <p> Actually looking at it again, looks like it would throw up some warnings with VC++ and it does indeed: </p> <pre class="wiki">basic_iarchive.cpp ..\..\..\libs\serialization\src\basic_iarchive.cpp(345) : warning C4267: 'argument' : conversion from 'size_t' to 'const unsigned int', possible loss of data ..\..\..\libs\serialization\src\basic_iarchive.cpp(380) : warning C4267: 'argument' : conversion from 'size_t' to 'const unsigned int', possible loss of data ..\..\..\libs\serialization\src\basic_iarchive.cpp(391) : warning C4267: 'argument' : conversion from 'size_t' to 'const unsigned int', possible loss of data ..\..\..\libs\serialization\src\basic_iarchive.cpp(470) : warning C4267: 'initializing' : conversion from 'size_t' to 'const unsigned int', possible loss of data compile-c-c++ ..\..\..\bin.v2\libs\serialization\build\msvc-9.0\debug\address-model-64\threading-multi\basic_iserializer.obj basic_iserializer.cpp compile-c-c++ ..\..\..\bin.v2\libs\serialization\build\msvc-9.0\debug\address-model-64\threading-multi\basic_oarchive.obj basic_oarchive.cpp ..\..\..\libs\serialization\src\basic_oarchive.cpp(279) : warning C4267: 'argument' : conversion from 'size_t' to 'const unsigned int', possible loss of data ..\..\..\libs\serialization\src\basic_oarchive.cpp(367) : warning C4267: 'argument' : conversion from 'size_t' to 'const unsigned int', possible loss of data compile-c-c++ ..\..\..\bin.v2\libs\serialization\build\msvc-9.0\debug\address-model-64\threading-multi\basic_oserializer.obj basic_oserializer.cpp </pre><p> ... and so on. </p> <p> It also throws up a bench of warnings about unsafe functions. I normally don't see those as _SCL_SECURE_NO_WARNINGS and _CRT_SECURE_NO_DEPRECATE get set in my build environment (not via bjam). </p> <p> So sorry about the confusion there. This was a patch I've been applying against boost for some time and I thought it was about time I mentioned it - but sadly forgot where it was generating the warnings in the first place! </p> <p> If I get some time I'll have a look with <a class="missing wiki">SunStudio</a> but hopefully the VC++ warnings can be removed in the meantime? </p> <p> Best regards </p> <p> Luke Elliott. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Robert Ramey</dc:creator> <pubDate>Sun, 15 Jul 2012 19:51:49 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/7010#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/7010#comment:4</guid> <description> <p> FYI, this is not so easy as it seems. </p> <p> it presumes that the underlying type of object_id_type is unsigned int. </p> <p> But in fact, it is uint_least32_t which may or may not be the same type as unsigned int. </p> <p> I'm still looking into this. </p> <p> Robert Ramey </p> </description> <category>Ticket</category> </item> </channel> </rss>