July 2004 - Boost - lists.boost.org

RE: [boost] Re: Boost.Threads: Do we need all those mutexes?
by Glen Knowles 10 Jul '04

10 Jul '04

> From: Howard Hinnant [mailto:hinnant@twcny.rr.com] > On Jul 9, 2004, at 11:00 PM, Glen Knowles wrote: > > >> <nod> I just implemented lock_both::lock two ways: Once > just keep > >> try-locking both ways, and once locking in the order of > the addresses > >> of the locks (with only two locks in the test, this was a safe > >> operator<). My test looks like: > > > > The problem case for spinning is when one thread gets the locks and > > the holds them for a non-trivial length of time. During > that time the > > other, spinning thread, just wastes cpu as fast as it can. > This just > > gets magnified as more threads are involved. > > You are describing a spin-lock, but not lock_both (except for > a theoretical and unlikely scenario). Yes, I didn't think it through all the way. Glen

1 0

RE: [boost] Re: Re: Re: Pretty Good Initialization Library
by Glen Knowles 10 Jul '04

10 Jul '04

> From: Vladimir Prus [mailto:ghost@cs.msu.su] > > As Andras Erdei the gap between people who know about special > properties of operator(), and those who know that overloaded > version does not have that properties is very, very narrow. FWIW, I knew that a comma was a sequence point from experience with C but didn't know (never thought about) that it lost that property when overloaded in C++. Glen

1 0

RE: [boost] Re: Boost.Threads: Do we need all those mutexes?
by Glen Knowles 10 Jul '04

10 Jul '04

> From: Matt Hurd [mailto:matt.hurd@gmail.com] > > Holding multiple locks is pretty common and necessary. If > you can guarantee they will always be acquired in the same > order they will not deadlock. It is necessary. :) > > AFAIK r/w locks only makes sense if you're going to hold read locks > > for a period of time, otherwise you're better off just > using a regular mutex. > > Concurrency may be better with shared access. > > The most common case for me is for collections. Multi-read > might be quite important to your application's concurrent performance. My logic is that using a read lock only improves concurrency over exclusion for that period of time that you hold the lock. If that period is short any improvement will likely be insignificant next to what you paid for hitting the memory barrier in either case. Of course, YMMV :) Glen

1 0

RE: [boost] Re: Boost.Threads: Do we need all those mutexes?
by Glen Knowles 10 Jul '04

10 Jul '04

> From: Howard Hinnant [mailto:hinnant@twcny.rr.com] > On Jul 9, 2004, at 7:10 PM, Glen Knowles wrote: > >> Without try locks, lock_both can't be made to work without risking > >> deadlock. > > > > Lock_both can be made to work with try locks? Either you > have a way to > > deterministicly set the order you lock the mutexes or you have > > problems. You can avoid deadlocking with try lock, but you > will fail > > to get the pair of locks in cases were you would have gotten it by > > waiting. I suppose you could just keep try-locking both > ways until you > > get it, but that's not good for performance. :) > > Well actually keep try-locking both ways is what I've been > doing. I'd agree with you that in a heavily contested > context, performance could theoretically suffer arbitrarily badly. > > > One solution to this problem would be mutex::operator< > > <nod> I just implemented lock_both::lock two ways: Once > just keep try-locking both ways, and once locking in the > order of the addresses of the locks (with only two locks in > the test, this was a safe operator<). My test looks like: The problem case for spinning is when one thread gets the locks and the holds them for a non-trivial length of time. During that time the other, spinning thread, just wastes cpu as fast as it can. This just gets magnified as more threads are involved. Glen

2 1

Boost sandbox
by Edward Diener 10 Jul '04

10 Jul '04

How does one access files in the Boost sandbox ? I am particular interested in libraries that have been reviewed and approved after the 1.31 release. When I get the latest Boost from CVS I do not see those libraries there. I am assuming they are somewhere, perjaps in the sandbox. How can I get them to try them out before the next release of Boost ?

2 3

Latest CVS doc links broken
by Edward Diener 10 Jul '04

10 Jul '04

The documentation links for lambda and thread in the latest Boost CVS do not go to a valid page.

1 0

[regression] Link failures for intel-win32-7.1-vc6-stlport-4.5.3
by Rene Rivera 10 Jul '04

10 Jul '04

Before John Maddock left on vacation, lucky him, he asked me to look into how to fix the problems with linking failing under some circumstances for this toolset in the regression tests. His supposition was that the auto-linking was not generating the correct name for linking, and that we needed to fix either the auto-linking or the build to be consistent about the naming. In looking at what is failing, as compared to what is not failing, my conclusion differs. The problem is that the failing tests are using auto-linking at all. As according to John himself one should not use it in the regression tests: "Please note however that this Jamfile will only build with compilers that do actually support auto-linking, so it should not be added to the regular regression tests." (http://boost.org/more/separate_compilation.html#testing) -- And the tests in question, signals, accidentally use both auto-linking and direct linking. There are two ways of fixing this problem: a) I automatically and globally <define>BOOST_ALL_NO_LIB=1 for all targets within Boost, or, b) We change individually each test that uses an auto-link enabled library to <define>BOOST_ALL_NO_LIB=1 I'm currently leaning towards (b), even if it is more work, as it has less chances of breaking other tests and/or the regular builds of examples and the libraries themselves. Comments? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq

2 4

Proposed patch to config/compiler/visualc.hpp
by Michael Glassford 10 Jul '04

10 Jul '04

Two minor changes for WinCE compatibility, to be used by Boost.Threads. I can commit the changes myself, but didn't want to mess with the config files without bringing it up here first. Mike Index: boost/config/compiler/visualc.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/config/compiler/visualc.hpp,v retrieving revision 1.37 diff -u -r1.37 visualc.hpp --- boost/config/compiler/visualc.hpp 22 Jun 2004 12:33:06 -0000 1.37 +++ boost/config/compiler/visualc.hpp 6 Jul 2004 17:44:02 -0000 @@ -17,7 +17,7 @@ // turn off the warnings before we #include anything #pragma warning( disable : 4503 ) // warning: decorated name length exceeded -#if _MSC_VER <= 1200 // 1200 == VC++ 6.0 +#if _MSC_VER <= 1201 // 1200 == VC++ 6.0, 1201 == EVC4.2 #pragma warning( disable : 4786 ) // ident trunc to '255' chars in debug info # define BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS # define BOOST_NO_VOID_RETURNS @@ -73,6 +73,11 @@ # define BOOST_NO_INTRINSIC_WCHAR_T #endif +#ifdef _WIN32_WCE +# define BOOST_NO_THREADEX +# define BOOST_NO_GETSYSTEMTIMEASFILETIME +#endif + // // check for exception handling support: #ifndef _CPPUNWIND

2 2

static_assert, documentation nit
by Glen Knowles 10 Jul '04

10 Jul '04

Near the beginning of the documentation on the website the example: Illegal use of COMPILE_TIME_ASSERTION_FAILURE<false> Should, I believe, read: Illegal use of STATIC_ASSERTION_FAILURE<false> Glen Knowles Centor Software Corporation

3 2

Problem with Linux test reports
by Joaquín Mª López Muñoz 10 Jul '04

10 Jul '04

Regression tests for Linux are updating OK every day, but the advanced developer and user reports seem to be stuck at Jul 5th. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 5