- Boost - lists.boost.org

ASIO Query
by james＠jamesbb.co.uk 21 Dec '11

21 Dec '11

Hiya, I'm hoping for opinions on using an io_service per core against a single io_service with multiple threads (similar to HTTP Server examples 2 & 3). The application is a TCP authentication / proxy server, intended to use all available cores. - The TCP streams consist of small messages (usually a few hundred bytes) which can individually be processed quickly. - Connections themselves are fairly long lasting - average around 4 hours, although occasionally up to 10-12 hours. We're looking for a 'shared nothing' design between threads - database queries can be made per-thread (using TLS), for example. The application is written for Redhat Linux - I'm unsure if it makes a difference. Any suggestions are much appreciated! Cheers Jim

1 0

[fusion] patch for #5010
by Jürgen Hunold 21 Dec '11

21 Dec '11

Hi, tow weeks ago I have attached a patch to https://svn.boost.org/trac/boost/ticket/5010 changing fusion::nil to fusion::nil_ for better compatibility with Obective-C and my case an ancient version of LEDA. Patch attached for convenience. The questions is how to proceed? May I commit the patch? Any documentation to change? Hoping for feedback, Yours, Jürgen -- Dipl.-Math. Jürgen Hunold | IVE mbH Software-Entwickler | Lützerodestraße 10 Tel: +49 511 897668 33 | 30161 Hannover, Germany Fax: +49 511 897668 29 | http://www.ivembh.de juergen.hunold(a)ivembh.de | | Geschäftsführer: Sitz des Unternehmens: Hannover | Univ.-Prof. Dr.-Ing. Thomas Siefer Amtsgericht Hannover, HRB 56965 | PD Dr.-Ing. Alfons Radtke

3 4

[config] Sandia-pgi-11.9 thread support
by Vicente J. Botet Escriba 21 Dec '11

21 Dec '11

Hi, on the regression test I see this error Test output: Sandia-pgi-11.9 - thread - test_barrier / pgi-11.9 Rev 76060 / Mon, 19 Dec 2011 10:30:05 +0000 *Report Time: *Mon, 19 Dec 2011 21:30:12 +0000 Compile [2011-12-19 12:43:58 UTC]: fail "pgCC" -INLINE:none -Kieee -fpic -fPIC -gopt -Minform=warn -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_NO_AUTO_LINK=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -D__need_IOV_MAX -I".." -c -o "/scratch/kbelco/boost/results/boost/bin.v2/libs/thread/test/test_barrier.test/pgi-11.9/debug/threading-multi/test_barrier.o" "../libs/thread/test/test_barrier.cpp" "../boost/config/requires_threads.hpp", line 86: catastrophic error: #error directive: "Compiler threading support is not turned on. Please consult your compiler's documentation for the appropriate options to use" # error "Compiler threading support is not turned on. Please consult your compiler's documentation for the appropriate options to use" ^ 1 catastrophic error detected in the compilation of "../libs/thread/test/test_barrier.cpp". Compilation terminated. Is something missing in the boost/config/requires_threads.hpp file? Best, Vicente

2 1

... broken with clang
by Beman Dawes 21 Dec '11

21 Dec '11

On Sat, Dec 17, 2011 at 6:42 AM, Andrey Semashev <andrey.semashev(a)gmail.com> wrote: >... All in all, I consider clang to be at a too early stage of development > to support it in the libraries. While I believe clang has a bright future, I'm afraid I agree with you. Clang's lack of support on Windows, including lack of installer, makes it hard for Windows developers to work with clang. Looking forward to the day when clang "just works" on Windows, --Beman

11 22

[iostreams] #5908: failure to parse optional fields in gzip header
by Travis Abbott 20 Dec '11

20 Dec '11

Hi, I'm wondering if anyone with commit access can have a look at this ticket/patch I put in a few months ago: https://svn.boost.org/trac/boost/ticket/5908 This is technically a regression, as it did work in 1.40, but support for multiple compressed files within 1 stream was not. When that was added, some refactoring was done which introduced this new bug. I actually need support for both of those features, so I'd really appreciate any consideration that can be given to this bug. Thanks, Travis Abbott

1 0

[Review Results:Algorithms] Boost.Algorithms is accepted
by Dave Abrahams 20 Dec '11

20 Dec '11

Having “reviewed the reviews” of Boost.Algorithms, I'm pleased to announce that it is unconditionally accepted. Congratulations to Marshall Clow! There were 5 yes votes and 1 no vote. The issues raised in all reviews were taken seriously by Marshall and recorded in the issue tracker at https://github.com/mclow/Boost.Algorithm I trust that Marshall will address the most important ones immediately, so I feel no need to place conditions on acceptance. Among the most important issues: https://github.com/mclow/Boost.Algorithm/issues/19 https://github.com/mclow/Boost.Algorithm/issues/18 https://github.com/mclow/Boost.Algorithm/issues/16 https://github.com/mclow/Boost.Algorithm/issues/15 https://github.com/mclow/Boost.Algorithm/issues/2 Thanks, everybody, for your participation! -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 1

Home page needs updating
by Nevin Liber 20 Dec '11

20 Dec '11

"Ten Boost libraries are already included in the C++ Standards Committee's Library Technical Report (TR1) and will be in the new C++0x Standard now being finalized. C++0x will also include several more Boost libraries in addition to those from TR1." Seems a bit out of date... :-) Nevin :-) -- Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> (847) 691-1404

2 1

[date_time] gcc 3.4.6 - int_adapter<T>::from_special(special_values) is not inlined, so duplicated (#6302)
by Vicente J. Botet Escriba 20 Dec '11

20 Dec '11

Hi, I know that gcc 3.4.6 is an old compiler version, but there are a lot of error on the Boost.Thread regression tests. I have created a ticket #6302 <https://svn.boost.org/trac/boost/ticket/6302> int_adapter<T>::from_special(special_values) is not inlined, so duplicated. <https://svn.boost.org/trac/boost/ticket/6302> to follow this issue It seems that this function template<typename int_type_> class int_adapter { static int_adapter from_special(special_values sv) { switch (sv) { case not_a_date_time: return not_a_number(); case neg_infin: return neg_infinity(); case pos_infin: return pos_infinity(); case max_date_time: return (max)(); case min_date_time: return (min)(); default: return not_a_number(); } } is not been inlined with gcc 3.4.6 and so it is duplicated at link time. See link error on regression test Test output: Sandia-gcc-3.4.6 - thread - test_condition_lib / gcc-3.4.6 Rev 76061 / Mon, 19 Dec 2011 12:54:33 +0000 Report Time: Mon, 19 Dec 2011 21:30:12 +0000 Compile [2011-12-19 13:33:17 UTC]: succeed "/sierra/Sntools/extras/compilers/gcc-3.4.6/bin/g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -pthread -fPIC -m32 -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_NO_AUTO_LINK=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_LIB=1 -I".." -c -o "/scratch/kbelco/boost/results/boost/bin.v2/libs/thread/test/test_condition_lib.test/gcc-3.4.6/debug/address-model-32/threading-multi/test_condition.o" "../libs/thread/test/test_condition.cpp" Link [2011-12-19 13:33:17 UTC]: fail "/sierra/Sntools/extras/compilers/gcc-3.4.6/bin/g++" -o "/scratch/kbelco/boost/results/boost/bin.v2/libs/thread/test/test_condition_lib.test/gcc-3.4.6/debug/address-model-32/threading-multi/test_condition_lib" -Wl,--start-group "/scratch/kbelco/boost/results/boost/bin.v2/libs/thread/test/test_condition_lib.test/gcc-3.4.6/debug/address-model-32/threading-multi/test_condition.o" "/scratch/kbelco/boost/results/boost/bin.v2/libs/thread/test/test_condition_lib.test/gcc-3.4.6/debug/address-model-32/threading-multi/tss_null.o" "/scratch/kbelco/boost/results/boost/bin.v2/libs/test/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_unit_test_framework.a" "/scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a" -Wl,-Bstatic -Wl,-Bdynamic -lrt -Wl,--end-group -g -pthread -m32 `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' referenced in section `.rodata' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o): defined in discarded section `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o) `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' referenced in section `.rodata' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o): defined in discarded section `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o) `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' referenced in section `.rodata' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o): defined in discarded section `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o) `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' referenced in section `.rodata' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o): defined in discarded section `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o) `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' referenced in section `.rodata' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o): defined in discarded section `.gnu.linkonce.t._ZN5boost9date_time11int_adapterIxE12from_specialENS0_14special_valuesE' of /scratch/kbelco/boost/results/boost/bin.v2/libs/thread/build/gcc-3.4.6/debug/address-model-32/link-static/threading-multi/libboost_thread.a(thread.o) collect2: ld returned 1 exit status Is this a know error for this compiler version? Best, Vicente

4 5

[predef][review-request] Requesting a review of Predef library submission..
by Rene Rivera 20 Dec '11

20 Dec '11

I've completed doing a final pass at the documentation and code for the Predef library. And hence I'm requesting the library be placed in the review "queue" (aka the review bucket). For those who missed it.. The Predef library implements two simple tasks: 1. Definition of a single version number macro to provide consistent version number at the preprocessor level. 2. A collection of detected definitions for compilers, standard libraries, architectures, operating systems, and languages. Unlike the Boost Config Library it doesn't define language features and capabilities. But only defines presence of detected compilation context. Documentation and downloads are available in the sandbox.. * Documentation at <http://tinyurl.com/7yrodwx> * Subversion source at <http://tinyurl.com/75oggaq> * Zip with Windows EOLs at <http://tinyurl.com/6lt7pks> * Bz2 with Unix LF-EOLs at <http://tinyurl.com/73n6a3k> Rene. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

4 4

[1.48.0] Beta 1 release candidates available
by Beman Dawes 20 Dec '11

20 Dec '11

Release candidate files for 1.48.0 beta 1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. Thanks, --The release managers

21 44