boost.lockfree is now in trunk and it passes the tests on most supported platforms. atm it includes a private copy of boost.atomic, which will be removed once boost.atomic is merged (helge wanted to do it quite soon) ... there are still some test failures on win32, but i think i found the reason and fixed the tests (btw it is rather time consuming to work with the test farm as the win32 tests are only run about once a week). It's doing better but "stack overflow"?
<http://www.boost.org/development/tests/trunk/developer/output/KTC-Win7x64_VC10x64-boost-bin-v2-libs-lockfree-test-queue_test-test-msvc-10-0-debug-address-model-64-threading-multi.html> <http://www.boost.org/development/tests/trunk/developer/output/KTC-Win7x64_VC10x64-boost-bin-v2-libs-lockfree-test-stack_test-test-msvc-10-0-debug-address-model-64-threading-multi.html>
same `stack overflow' that i've seen in some other win32 tests ... it seems that win32 does not like that to allocate large objects on the stack ...
should be fixed
Fixed "stack test", but "queue test" still fail. Doesn't really say why though.
the queue test has three stress tests (like the stack) ... however the queue is more complex than the stack ... the output comes from these stress tests: threads created writer threads joined, waiting for readers reader threads joined threads created writer threads joined, waiting for readers reader threads joined threads created this suggests that either the third test case fails, or that that it gets killed at some point. just to confirm, do you have a timeout for the tests? thanks, tim