- Boost - lists.preview.boost.org

RE: [boost] Re: Regression results for Intel 8 online
by Michael Stevens 21 Jul '04

21 Jul '04

Stefan thanks for you work and the reply On Wednesday 21 July 2004 10:15, "Stefan Slapeta" <stefan(a)slapeta.com> wrote: > Did you see the __declspec(dllimport)? Should this be ok? > > test21.obj : error LNK2019: unresolved external symbol > "__declspec(dllimport) public: __thiscall > std::complex<float>::complex<float>(class std::complex<float> const &)" etc. > > test21.obj : error LNK2019: unresolved external symbol I saw it but don't really know what to make of it! Essentially uBLAS just makes use of the system <complex> header. How this result in an unresolved symbol I don't know. My wild guess the they are normally for it the compiler runtime, and something has gone haywire! > "C:\Programme\Intel\CPP\Compiler80\Ia32\bin\icl" /Zm800 -nologo -GX -c > -DBOOST_UBLAS_USE_INTERVAL /Z7 /Od /Ob0 /GX /GR /MDd /Op /Zc:forScope > /Zc:wchar_t /Qwn5 /Qwd985 -Qoption,c,--arg_dep_lookup /Qansi_alias > -D_NATIVE_WCHAR_T_DEFINED /Qvc7.1 I am really guessing here as I don't have manuals! The /Z7 and /Qv7.1 look interesting. I think the /Z7 is specifying old style debug symbols which is a bit odd. I guess they are usually smaller then the "edit and continue" symbols. /Qv7.1 I assume is enabling VC 7.1 compatibility bugs and all. I guess this adds a few extra bugs of Intels own. I not sure why the default build options for boost have this in. Anyone know? Do you think it would be appropriate to do the regression testing in the compilers native mode? Thanks, Michael

2 1

RE: [boost] Re: What is it with boost and tinyurl?
by Rozental, Gennadiy 21 Jul '04

21 Jul '04

> > Too much trouble. I certainly wouldn't want to set that policy; it > > would just discourage posting links. > > Too much trouble? An extra Ctrl+V is too much trouble for > someone who doesn't mind opening tinyurl.com, pasting the > link there, copying the result, and pasting it back? Actually it's only one click http://tinyurl.com/#toolbar Gennadiy.

1 0

RE: Boost.Test problems (Was: [boost] Multiple link definitions o n Darwin tests)
by Rozental, Gennadiy 21 Jul '04

21 Jul '04

>A change to Boost.Test basically means all > tests will have to be recompiled on the testing machines. > This means test results will be available at a lower > frequency. A higher frequency is very desirable during the > release preparations. I did 1(one) update during this release preparation. It included mainly only license text update. I don't believe Boost.Test modification interfere with frequency of regression test run. Gennadiy.

1 0

RE: Boost.Test problems (Was: [boost] Multiple link definitions o n Darwintests)
by Rozental, Gennadiy 21 Jul '04

21 Jul '04

> Thank you Peter. After the release, I'll definitely move > Spirit to use this simple, no frills, test utility. The > requirements for such a facility should be 1) Works 100% on > *ALL* compilers 2) Is transparent and does not get in the way > (you can pretend it's not there at all) 3) Is 100% stable (no > frequent API changes) > 4) Is as simple as possible (less chance for Murphy's law to > kick in). IMO, Boost.Test does not satisfactorily satisfy > these requirements. Boost.Test minimal testing facility practically did not change since the day it was introduced (maybe only licence test updates). Gennadiy.

1 0

Re:[boost] Problems with program_options using GCC 3.4 on FreeBSD
by Robert Ramey 21 Jul '04

21 Jul '04

Jonathan Wakely wrote: >I've just tried building the program_options library, using GCC 3.4.1 >on FreeBSD 4.8 and hit a couple of compilation errors. >One error is caused by the platform, one by the compiler's stdlib. Any chance we might convince you to run the whole test suite on the platform? I would be curious as to the results for the serialization library here. Robert Ramey

2 1

Re: Boost.Test problems (Was: [boost] Multiple link definitions on Darwintests)
by Robert Ramey 21 Jul '04

21 Jul '04

>Joel de Guzman wrote: >Peter Dimov wrote: >> Vladimir Prus wrote: >> >>>Of all Boost.Test functionality I use only 'test_main' and >>>BOOST_CHECK, and I'd be really gratefull if that subset just worked. >> >> #include <boost/detail/lightweight_test.hpp> >> >> int main() >> { >> int x = 0; >> >> BOOST_TEST( ++x == 1 ); >> BOOST_TEST( ++x == 1 ); >> >> return boost::report_errors(); >> } >From the very beginning I've been using: #include <boost/test> Int main(){ BOOST_CHECK(...); Return boost:success; } I've never had a problem and have been pleased as punch. Robert Ramey

1 0

Wow, lotsa updates last night
by Victor A. Wagner Jr. 21 Jul '04

21 Jul '04

The full log is in the usual place ( ftp://rudbek.com/pub/boost/status.log ) I attempted to "fix" the lower and upper ambiguous symbols by changing lower(value) to value.lower() and the same for upper(value), but that causes problems later in the compile when apparently some ublas things are being used. .....perhaps the solution will be to add the required methods lower()const and upper()const to the ublas system. at any rate, here are the "interesting" lines: File: status.log ...found 38391 targets... ...using 2 temp targets... ...updating 4251 targets... ...on 100th target... ...on 200th target... ...on 300th target... ...on 400th target... C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'lower' : ambiguous symbol C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'upper' : ambiguous symbol ...failed vc-C++ ..\bin\boost\libs\numeric\ublas\test7.test\vc7.1\debug\test71.obj... C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'lower' : ambiguous symbol C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'upper' : ambiguous symbol ...failed vc-C++ ..\bin\boost\libs\numeric\ublas\test7.test\vc7.1\debug\test72.obj... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.CMD for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test71.obj... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.exe for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.CMD... ...on 500th target... ...on 600th target... ...on 700th target... ...on 800th target... ...on 900th target... ...on 1000th target... ...on 1100th target... ...on 1200th target... ...on 1300th target... ...on 1400th target... ...on 1500th target... ...on 1600th target... ...on 1700th target... ...on 1800th target... ...on 1900th target... ...on 2000th target... ...on 2100th target... ...on 2200th target... ...on 2300th target... ...on 2400th target... ..\libs\multi_array\test\fail_ref_cview3.cpp(54) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_cview2.cpp(48) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_array_view<NDims>::type' to 'boost::detail::multi_array::multi_array_view<T,NumDims>' ..\libs\multi_array\test\fail_ref_cview.cpp(52) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_csubarray3.cpp(49) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_csubarray2.cpp(45) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_reference' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_ref_csubarray.cpp(45) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::multi_array_impl_base<T,NumDims>::const_subarray<NDims>::type' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_ref_criterator.cpp(30) : error C2440: 'initializing' : cannot convert from 'boost::reverse_iterator<Iterator>' to 'boost::reverse_iterator<Iterator>' ..\libs\multi_array\test\fail_ref_cparen.cpp(41) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_citerator.cpp(30) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' to 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' ..\libs\multi_array\test\fail_ref_cdata.cpp(38) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_ref_cbracket.cpp(41) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_cview3.cpp(56) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_cview2.cpp(52) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_array_view<NDims>::type' to 'boost::detail::multi_array::multi_array_view<T,NumDims>' ..\libs\multi_array\test\fail_cview.cpp(55) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_csubarray3.cpp(46) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_csubarray2.cpp(42) : error C2440: 'initializing' : cannot convert from 'boost::multi_array_ref<T,NumDims>::const_reference' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_csubarray.cpp(43) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::multi_array_impl_base<T,NumDims>::const_subarray<NDims>::type' to 'boost::detail::multi_array::sub_array<T,NumDims>' ..\libs\multi_array\test\fail_criterator.cpp(30) : error C2440: 'initializing' : cannot convert from 'boost::reverse_iterator<Iterator>' to 'boost::reverse_iterator<Iterator>' ..\libs\multi_array\test\fail_cparen.cpp(41) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_citerator.cpp(30) : error C2440: 'initializing' : cannot convert from 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' to 'boost::detail::multi_array::array_iterator<T,TPtr,NumDims,Reference>' ..\libs\multi_array\test\fail_cdata.cpp(39) : error C2166: l-value specifies const object ..\libs\multi_array\test\fail_cbracket.cpp(37) : error C2166: l-value specifies const object C:\Projects\boost\boost\archive\detail\iserializer.hpp(215) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' ...on 2500th target... ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2784: 'bool std::operator ==(const std::allocator<_Ty> &,const std::allocator<_Other> &)' : could not deduce template argument for 'const std::allocator<_Ty> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2784: 'detail::enable_if_interoperable<Derived1,Derived2,mpl::apply2<boost::detail::always_bool2,Derived1,Derived2>::type>::type boost::operator ==(const boost::iterator_facade<Derived1,V1,TC1,R1,D1> &,const boost::iterator_facade<Derived2,V2,TC2,R2,D2> &)' : could not deduce template argument for 'const boost::iterator_facade<Derived,Value,CategoryOrTraversal,Reference,Difference> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2784: 'bool std::operator ==(const std::istream_iterator<_Ty,_Elem,_Traits,_Diff> &,const std::istream_iterator<_Ty,_Elem,_Traits,_Diff> &)' : could not deduce template argument for 'const std::istream_iterator<_Ty,_Elem,_Traits,_Diff> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2784: 'bool std::operator ==(const std::istreambuf_iterator<_Elem,_Traits> &,const std::istreambuf_iterator<_Elem,_Traits> &)' : could not deduce template argument for 'const std::istreambuf_iterator<_Elem,_Traits> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2784: 'bool std::operator ==(const std::reverse_iterator<_RanIt> &,const std::reverse_iterator<_RanIt> &)' : could not deduce template argument for 'const std::reverse_iterator<_RanIt> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2784: 'bool std::operator ==(const std::pair<_Ty1,_Ty2> &,const std::pair<_Ty1,_Ty2> &)' : could not deduce template argument for 'const std::pair<_Ty1,_Ty2> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(57) : error C2677: binary '==' : no global operator found which takes type 'iter_t' (or there is no acceptable conversion) ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(58) : error C2186: '+' : illegal operand of type 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(59) : error C2784: 'detail::enable_if_interoperable<Derived1,Derived2,mpl::apply2<boost::detail::always_bool2,Derived1,Derived2>::type>::type boost::operator <(const boost::iterator_facade<Derived1,V1,TC1,R1,D1> &,const boost::iterator_facade<Derived2,V2,TC2,R2,D2> &)' : could not deduce template argument for 'const boost::iterator_facade<Derived,Value,CategoryOrTraversal,Reference,Difference> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(59) : error C2784: 'bool std::operator <(const std::reverse_iterator<_RanIt> &,const std::reverse_iterator<_RanIt> &)' : could not deduce template argument for 'const std::reverse_iterator<_RanIt> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(59) : error C2784: 'bool std::operator <(const std::pair<_Ty1,_Ty2> &,const std::pair<_Ty1,_Ty2> &)' : could not deduce template argument for 'const std::pair<_Ty1,_Ty2> &' from 'void' ..\libs\spirit\test\fixed_size_queue_fail_tests.cpp(59) : error C2677: binary '<' : no global operator found which takes type 'boost::spirit::impl::fsq_iterator<QueueT,T,PointerT>' (or there is no acceptable conversion) ...on 2600th target... FAIL :: Get time of day micro second clock not supported due to inadequate compiler ...failed execute-test ..\bin\boost\libs\date_time\test\testmicrosec_time_clock.test\vc7.1\debug\testmicrosec_time_clock.run... ...on 2700th target... ...on 2800th target... ...on 2900th target... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.run for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.exe... ...on 3000th target... ...on 3100th target... ...on 3200th target... ...on 3300th target... ...on 3400th target... ...on 3500th target... ...on 3600th target... ...on 3700th target... ...on 3800th target... ...on 3900th target... ...on 4000th target... ...on 4100th target... **** error return code: -1 ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail4.test\vc7.1\debug\prg_exec_fail4.run... ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail3.test\vc7.1\debug\prg_exec_fail3.run... ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail2.test\vc7.1\debug\prg_exec_fail2.run... **** exception(205): C string: Test error by throwing C-style string exception ...failed RmTemps ..\bin\boost\libs\test\test\prg_exec_fail1.test\vc7.1\debug\prg_exec_fail1.run... ../libs/test/test/test_exec_fail4.cpp(22): error in "call_test_main": Msg Exception in "call_test_main": C string: Test error by throwing C-style string exception ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail4.test\vc7.1\debug\test_exec_fail4.run... ../libs/test/test/test_exec_fail3.cpp(23): error in "call_test_main": test v == 2 failed ../libs/test/test/test_exec_fail3.cpp(24): error in "call_test_main": test 2 == v failed ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail3.test\vc7.1\debug\test_exec_fail3.run... ../libs/test/test/test_exec_fail2.cpp(25): error in "call_test_main": test v == 2 failed ../libs/test/test/test_exec_fail2.cpp(26): error in "call_test_main": sample BOOST_ERROR call ../libs/test/test/test_exec_fail2.cpp(27): fatal error in "call_test_main": test 2 == v failed ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail2.test\vc7.1\debug\test_exec_fail2.run... C:/Projects/boost/libs/test/build/../src/test_main.cpp(40): error in "call_test_main": test test_main_result == 0 || test_main_result == boost::exit_success failed ...failed RmTemps ..\bin\boost\libs\test\test\test_exec_fail1.test\vc7.1\debug\test_exec_fail1.run... ../libs/test/test/ifstream_line_iterator_test.cpp(28): error in "test_default_delimeter": test it != utf::ifstream_line_iterator() failed ../libs/test/test/ifstream_line_iterator_test.cpp(30): error in "test_default_delimeter": test *it == "acv ffg" failed [ != acv ffg] ../libs/test/test/ifstream_line_iterator_test.cpp(36): error in "test_default_delimeter": test *it == " " failed [ != ] ../libs/test/test/ifstream_line_iterator_test.cpp(39): error in "test_default_delimeter": test *it == "1" failed [ != 1] ../libs/test/test/ifstream_line_iterator_test.cpp(51): error in "test_custom_delimeter": test it != utf::ifstream_line_iterator() failed ../libs/test/test/ifstream_line_iterator_test.cpp(53): error in "test_custom_delimeter": test *it == "{ abc d " failed [ != { abc d ] ../libs/test/test/ifstream_line_iterator_test.cpp(56): error in "test_custom_delimeter": test *it == "\n{ d \n dsfg\n" failed [ != ../libs/test/test/ifstream_line_iterator_test.cpp(59): error in "test_custom_delimeter": test *it == "\n" failed [ != ...failed execute-test ..\bin\boost\libs\test\test\ifstream_line_iterator_test.test\vc7.1\debug\ifstream_line_iterator_test.run... ...on 4200th target... ..\libs\test\test\minimal_test.cpp(66): Some error in function: 'int __cdecl test_main(int,char *[])' ...failed RmTemps ..\bin\boost\libs\test\test\minimal_test.test\vc7.1\debug\minimal_test.run... ...failed updating 13 targets... ...skipped 24 targets... ...updated 4214 targets... Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

Regression results for Intel 8 online
by Stefan Slapeta 21 Jul '04

21 Jul '04

I've put them here: http://genericprogramming.com/boost Failures: - ublas (2) - test (_many_)!! - thread/test_read_write_mutex like on other compilers - random(2) - date_time/testmicrosec_time_clock -> should be expected??? Furthermore some in range and serialization. Spirit is missing somehow; were the tests not included when the source was moved to boost CVS? Stefan

9 14

Latest read_write_mutex regression results
by Michael Glassford 21 Jul '04

21 Jul '04

The latest regression results for test_read_write_mutex at http://boost.sourceforge.net/regression-logs/cs-Linux/developer/thread.html report a number of different errors on different compilers, the most common being <quote> Assertion failed: valid_read_lock(m_state), file C:\Users\administrator\main\boost\libs\thread\build\..\src\read_write_mutex.cpp, line 218 </quote> This indicates to me that these regression tests were run without the changes I checked in yesterday afternoon. Is this just because it takes so long to run regression tests that I have to wait for the next run to find out how my changes worked, or is there another reason? Also, the only reason I can tell that the regression tests were run without recent changes is because the changes were significant enough that the assertion in question is no longer anywhere near line 218. Is there any possibility at some point in the future of adding information to the regression log indicating what version of each source file was used to run the tests? I realize that this information isn't directly available to the regression testing tools, but perhaps the build process could be modified to record the cvs version information for each source file it uses (not sure how it would get it) whenever it builds anything, and the information could be incorporated into the regression reports? Mike

2 1

Re:Re: [boost] Serialization and tmpnam
by Robert Ramey 21 Jul '04

21 Jul '04

>> [1] As does the manpage say: "Never use this function". >Depending on the version, you may even see a more helpful message in the >manpage. >BUGS > Never use this function. Use mkstemp(3) instead. Well, not helpful enough. Making a stream from a file descriptor is code I don't have. Robert Ramey.

6 12