- Boost - lists.boost.org

[Review] xpressive review period extended
by Thomas Witt 22 Sep '05

22 Sep '05

Hi, after being declared half-closed (my bad) the review period for Eric Niebler's xpressive library has now been extended until Sunday Sep 25. The original announcement can be found here: http://tinyurl.com/dk2yz Some additional information is in this posting: http://tinyurl.com/dphjc Thomas Review Manager xpressive

1 0

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 22 Sep '05

22 Sep '05

In-Reply-To: <dgmfeo$q1v$1(a)sea.gmane.org> kalita(a)poczta.onet.pl (Marcin Kalicinski) wrote (abridged): > I think generally this is a good idea, but it has a small problem. I > would expect that BOOST_ASSUME should turn into __assume when compiled > in "release" mode of MSVC. As of above proposed solution this is not > the case - user additionally needs to define BOOST_DISABLE_ASSERTS to > get __assume. So when NDEBUG is defined and BOOST_DISABLE_ASSERTS is > not (I think this is 99% of cases, because few people actually use > BOOST_DISABLE_ASSERTS), BOOST_ASSUME will expand to BOOST_ASSERT and > the whole thing will be useless. I did not use NDEBUG because BOOST_ASSERT doesn't, and I didn't want to revisit that decision. I imagine the policy is to use fine-grained flags and then add: #ifdef NDEBUG #define BOOST_DISABLE_ASSERTS #endif in a user-editable header somewhere. Arguably there should be a BOOST_DISABLE_ASSUMES, too, but for now I'll use BOOST_DISABLE_ASSERTS. > # define BOOST_ASSUME(e) { BOOST_ASSERT(e); if (e); else __assume(0); } That evaluates e twice, and if e is false it is not clear whether the assert will actually do anything because it could be optimised away. I think: # define BOOST_ASSUME(e) __assume(e) is simpler and better. > There's also a question what should BOOST_ENABLE_ASSERT_HANDLER do with > BOOST_ASSUME? Should it invoke the handler if condition is false? Only if BOOST_DISABLE_ASSERTS is not defined. So the full code would be: #include <boost/config.hpp> #if defined(BOOST_MSVC) && defined(BOOST_DISABLE_ASSERTS) # define BOOST_ASSUME(e) __assume(e) #else # define BOOST_ASSUME(e) BOOST_ASSERT(e) #endif -- Dave Harris, Nottingham, UK.

4 3

Errors compiling multi_index hashed.cpp
by David Crayford 22 Sep '05

22 Sep '05

Hi all, I've recently= downloaded boost to run on an IBM mainfram z/OS system (a port of vacpp). = I'm trying to compile multi_index\example\hashed.cpp (which I called stuf= f.cpp) and I'm getting the following errors. I'm a relative newbie with= C++ so I'm completely bamboozled by the compiler errors. Help with this wi= ll be greatly appreciated as I am currently in the process of trying to con= vince management to switch to C++ from C, and boost is one of my big hittin= g selling points. "/FTS1/tmp/doc/boost/mpl/aux_/integral_wrappe= r.hpp", line 85.30: CCN5431 (S) The declarator cannot be qualified with the= enclosing namespace "mpl_". = ; &n= bsp; ; &n= bsp; = ; &n= bsp; ; &n= bsp; = ; "'DOC.USER.CPP(STUFF)'", line 47.= 60: CCN6281 (W) "offsetof" cannot be applied to "struct word_counter_en= try". It is not a POD (plain old data) type. &= nbsp; &nbs= p; & nbsp; &nbs= p; &= nbsp; &nbs p; &= nbsp; &nbs= p; &= nbsp; "'DOC.USER.CPP(STUFF)'", line= 47.60: CCN6281 (W) "offsetof" cannot be applied to "struct word_counter= _entry". It is not a POD (plain old data) type.&n= bsp; = ; &n bsp; = ; &n= bsp; = ; &n bsp; = ; &n= bsp; "'DOC.USER.CPP(STUFF)'",= line 47.60: CCN6281 (W) "offsetof" cannot be applied to "struct word_cou= nter_entry". It is not a POD (plain old data) typ= e. &= nbsp; &nbs p; &= nbsp; &nbs= p; & nbsp; &nbs= p; &= nbsp; &nbs p; "'DOC.USER.CPP(STUFF= )'", line 51.59: CCN6281 (W) "offsetof" cannot be applied to "struct word= _counter_entry". It is not a POD (plain old dat= a) type. &= nbsp; &nbs p; &= nbsp; &nbs= p; & nbsp; &nbs= p; &= nbsp; &nbs p; "'DOC.USER.CPP= (STUFF)'", line 51.59: CCN6281 (W) "offsetof" cannot be applied to "struct = word_counter_entry". It is not a POD (plain old= data) type. &nb= sp; &nb= sp; = &nb= sp; &nb= sp; "'DOC.USER= .CPP(STUFF)'", line 51.59: CCN6281 (W) "offsetof" cannot be applied to "str= uct word_counter_entry". It is not a POD (plain= old data) type. = ; &n= bsp; ; &n= bsp; = ; &n= bsp; ; &n= bsp; "/FTS1= /tmp/doc/boost/mpl/aux_/integral_wrapper.hpp", line 85.30: CCN5431 (S) = The declarator cannot be qualified with the enclosing namespace "mpl_= ". &= nbsp; &nbs p; &= nbsp; &nbs= p; & nbsp; &nbs= p; &= nbsp; &nbs p; &= nbsp; "/FTS1/tmp/doc/boost/mpl/has_key.hpp", line 32.20: CCN5408 (S) = The base class "apply<boost::mpl::set0<mpl_::na>, &nb= sp; boost::multi_index::detail::duplicate_tag_mark>" is d eclared but not defined. &nb= sp; = &nb sp; = "/FTS1/tmp/doc/boost/multi_index/det ail/no_duplicate_tags.hpp", line 60.23: CCN5700 (I) The previous messag= e was produced while processing "struct boost::mpl::has_key&l t;boost::mpl::set0<mpl_::na>,boost::multi_index::detail::duplicat e_tag_mark>". &= nbsp; "/FTS1/tmp/doc/boost/type_traits/= is_base_and_derived.hpp", line 200.41: CCN5016 (S) The expression mus= t be an integral constant expression. &n= bsp; = ; &n bsp; = ; &n= bsp; = ; &n bsp; = ; &n= bsp; = ; "/FTS1/tmp/doc/boost/type_traits/is_base_and_deri= ved.hpp", line 200.33: CCN5700 (I) The previous message was produced while& nbsp; processing "boost::detail:: is_base_and_derived_impl<boost::multi_index::detail::tag_m ar= ker,boost::multi_index::tag<mpl_::na, &= nbsp; mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na ,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl _::= na,mpl_::na, mpl_::na,mpl_::na,mpl_::na= ,mpl_::na,mpl_::na> >::value". = ; &n= bsp; = ; &n bsp; = ; &n= bsp; "/FTS1/tmp/doc/boost/type_traits/i= s_base_and_derived.hpp", line 188.8: CCN5700 (I) The previous message= was produced while p= rocessing "struct boost::detail::is_base_and_derived_impl<boost: :multi_index::detail::tag_marker,boost::multi_index::tag<mpl_: :n= a, mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mp l_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_ ::na,= mpl_::na, mpl_::na,mpl_::na,mpl_::na,mp= l_::na,mpl_::na> >". &nb= sp; = &nb= sp; &nb= sp; "/FT= S1/tmp/doc/boost/type_traits/is_base_and_derived.hpp", line 209.7: = CCN6269 (S) The template argument for the non-type template parameter= of type "bool" must be an integral constant expression. &= nbsp; &nbs= p; & nbsp; &nbs= p; &= nbsp; "/FTS1/tmp/doc/boost/multi_index/tag.hpp", line 61.37: CCN5700 (I) The p= revious message was produced while processing "struct &nbs p; boost::is_base_and_derived<boost::multi_index::de tail::tag_marker,boost::multi_index::tag<mpl_::na,mpl_::na,mpl = _::na,mpl_::na, mpl_::na,mpl_::na,mpl _::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_: :na,m= pl_::na,mpl_::na,mpl_::na,mpl_::na,mpl_::na, &nb sp; mpl_::na,mpl_::na> >". = ; &n= bsp;

2 2

Boost publicity - article authors?
by Matthew Vogt 21 Sep '05

21 Sep '05

If anyone is interested in writing a brief article publicising boost, the Linux Weekly News (which covers open-source software as much as Linux) would be interested in receiving a submission. If anybody (maybe Björn Karlsson?) has suitable copy ready, the contact details are forwarded below: Matt lwn(a)lwn.net (LWN.net) Sent by: lwn(a)lwn.net 21/09/2005 06:36 AM To: mvogt(a)jupiters.com.au cc: Subject: Re: LWN Development page should cover boost releases Greetings Matt, thanks for the info on Boost. We're always looking for guest authors, if you would be interested in writing up a summary of the Boost project, that would make a good LWN development page lead article. We typically pay around $75 for such articles. We have an author guide here: http://lwn.net/op/AuthorGuide.lwn -Forrest Cook LWN.net - your Linux information source lwn(a)lwn.net -- Matthew Vogt mattvogt(a)warpmail.net -- http://www.fastmail.fm - mmm... Fastmail...

1 0

[wave] build hangs on GNU/Linux/amd64
by Russell Kliese 21 Sep '05

21 Sep '05

I've been trying to build boost on an amd64 machine under Debian Linux but it hangs trying to compile part of the wave library. Is it possible to skip building the wave library as a temporary work around (I am not familiar with jam)? I'm using the deb source package (from 1.33.0) from the unstable Debian distribution: http://packages.debian.org/unstable/source/boost I am building on the stable distribution (i.e. trying to create a back port because of the broken timed mutexes in 1.32). The build gets to: "g++" -c -Wall -ftemplate-depth-255 -D_REENTRANT -g -O0 -fno-inline -pthread -I"bin/boost/libs/wave/build" -I"/home/users/russell/cvs/debPackages/boost/boost_1_33_0" -I "/home/users/russell/cvs/debPackages/boost/boost_1_33_0" -o "bin/boost/libs/wave/build/libboost_wave.a/gcc/debug/threading-multi/instantiate_cpp_literalgrs.o" "/home/users/russell/cvs/debPackages/boost/boost_1_33_0/libs/wave/build/../src/instantiate_cpp_literalgrs.cpp" "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug "bin/boost/libs/wave/build/libboost_wave.a/gcc/debug/threading-multi/instantiate_cpp_literalgrs.o" at which point it hangs (top shows cc1plus using 99.9% CPU). Please let me know if I can supply more info to help debug this problem. Russell Kliese

5 4

[bigint] operator< problem
by Janusz Piwowarski 21 Sep '05

21 Sep '05

Hello I have the problem with boost::bigint (from boost-sandbox). There's minimal example: #include "boost/bigint.hpp" int main (void) { boost::bigint b = 1; while ( b < 1001 ) b *= 10; } Loop never ends; is it known issue? Compiler g++ 3.4.2 (mingw) -- Regards, Janusz

1 0

Re: [boost] Checked Integral Class
by Matt Doyle 21 Sep '05

21 Sep '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org]On Behalf Of Rob Stewart > Sent: Friday, September 16, 2005 2:06 PM > To: boost(a)lists.boost.org > Cc: boost(a)lists.boost.org > Subject: Re: [boost] Checked Integral Class > > > From: "Matt Doyle" <mdoyle(a)a-m-c.com> > > > From: "michael toksvig" <michaeltoksvig(a)yahoo.com> > > > > > add two numbers in the 1-10 range, and you invariably end=20 > > > up with a number=20 > > > > in the 2-20 range > > > > Yep. However, when considering constrained ranges, I find it > > > surprising that the result would be *permitted* to exceed the > > > constraints of the inputs. > > > > IOW, I'd have expect the result to be constrained to be 2-10. > > > Yes, that means that combinations exist that violate that > > > constraint, but at least it wouldn't surprise me. > > > > > YES, that's exactly the point I was trying to make earlier > - you just = > > did a much better job of explaining it :) > > Thanks, if in fact I was addressing your concern. > > > IMO, the constraints and/or policies set forth when the > type was defined = > > must apply for the lifetime of the type. > > To be certain we're talking about the same thing, Michael and I > have been discussing the result of a computation. Built-in types > regularly undergo promotions when participating in such > expressions, so the question is whether something similar should > happen for a checked integral class and what form it should take. > > Michael was positing that the result type should account for the > full range of values possible from the computation. I argued > against that. > > I should also point out that built-in types don't behave that > way; they can overflow silently, but they don't magically gain > range. (The analogy isn't strong, but has some bearing, I > think.) I think we are talking about the same thing but from different angles, consider this simple case; typedef constrained_value<0, 10, policy> MyCV; MyCV a = 6; MyCv b = 8; MyCv c = a + b; // Should fail If the user wants "c" to be able to hold the result of "a + b" he should define a new type that would accommodate it. We are on the same page aren't we? > > -- > > Rob Stewart stewart(a)sig.com > Software Engineer http://www.sig.com > Susquehanna International Group, LLP using std::disclaimer; > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost > Scanned by Fortigate {X3BTB534}

4 4

[Test] 1.33 compile error for Win9x/ME targets
by Christopher Kohlhoff 21 Sep '05

21 Sep '05

I'm trying to use the Boost Test framework for unit testing in asio but it doesn't work for Win9x/ME targets without a minor fix. The problem is due to boost/test/impl/execution_monitor.ipp only checking for _WIN32_WINNT, when the #define for Win9x/ME is _WIN32_WINDOWS. I had to make the following change to get it to work: @@ -55,7 +55,7 @@ # define BOOST_MS_STRUCTURED_EXCEPTION_HANDLING -# ifndef _WIN32_WINNT +# if !defined(_WIN32_WINNT) && !defined(_WIN32_WINDOWS) # ifdef _WINBASE_ # warning Debugger check disabled. Either define _WIN32_WINNT or include Boost.Test header in front of winbase.h # else I also encountered this as an error, rather than a warning as intended, because #warning is not supported by MSVC. It should probably use #pragma message("...") instead. Cheers, Chris

2 1

Boost regression notification (2005-09-21 [RC_1_33_0])
by Douglas Gregor 21 Sep '05

21 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-21T15:24:10Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. utility/enable_if Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 112 failures in 9 libraries: concept_check (20) foreach (1) graph (5) random (1) range (3) serialization (55) thread (8) utility/enable_if (16) wave (3) |concept_check| stl_concept_covering: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux intel-win32-8_1 intel-win32-9_0 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux dijkstra_heap_performance: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 |thread| test_barrier_lib: intel-9.0-linux test_condition_lib: intel-9.0-linux test_mutex_lib: intel-9.0-linux test_once_lib: intel-9.0-linux test_read_write_mutex_lib: intel-9.0-linux test_thread_lib: intel-9.0-linux test_tss_lib: intel-9.0-linux test_xtime_lib: intel-9.0-linux |utility/enable_if| constructors: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux dummy_arg_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lazy: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lazy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux member_templates: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux namespace_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux no_disambiguation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux partial_specializations: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: intel-9.0-linux

1 0

Boost regression notification (2005-09-21 [HEAD])
by Douglas Gregor 21 Sep '05

21 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-21T05:00:08Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. typeof Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 168 failures in 14 libraries: concept_check (14) filesystem (8) foreach (7) graph (4) math (3) mpl (2) parameter (17) python (1) regex (1) serialization (40) spirit (2) thread (24) typeof (41) wave (4) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 |filesystem| convenience_test: msvc default_name_check_test: msvc fstream_test: msvc large_file_support_test: msvc operations_test: msvc operations_test_dll: msvc path_test: msvc path_test_dll: msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |math| octonion_test: gcc-4_0-darwin quaternion_test: gcc-4_0-darwin special_functions_test: gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| data_members: msvc |regex| static_mutex_test: msvc |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| data_member_emulation: cw-9_4 data_member_native: intel-win32-9_0 intel-win32-9_0 function_emulation: cw-9_4 function_native: intel-win32-9_0 intel-win32-9_0 msvc function_ptr_emulation: cw-9_4 function_ptr_native: intel-win32-9_0 intel-win32-9_0 function_ref_emulation: cw-9_4 function_ref_native: intel-win32-9_0 intel-win32-9_0 lvalue_emulation: cw-9_4 lvalue_native: intel-win32-9_0 intel-win32-9_0 msvc member_function_emulation: cw-9_4 member_function_native: intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_emulation: cw-9_4 template_int_native: intel-win32-9_0 intel-win32-9_0 template_tpl_emulation: cw-9_4 template_tpl_native: intel-win32-9_0 intel-win32-9_0 msvc template_type_emulation: cw-9_4 template_type_native: intel-win32-9_0 intel-win32-9_0 type_emulation: cw-8_3 cw-9_4 cw-9_4 type_native: intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

1 0