- Boost - lists.preview.boost.org

[compute] review
by Sebastian Schaetz 17 Dec '14

17 Dec '14

Hi, Here is my review of Boost.Compute: 1. What is your evaluation of the design? The library is based upon OpenCL, a cross-platform cross-device open standard that abstracts access to and provides a programming model for many-core vector co-processors such as GPUs. These co-processors are usually referred to as "devices". The library provides a wrapper layer around the OpenCL C interface. It skips the standard OpenCL C++ wrapper which I don't consider a problem because except for destructors there is no added value in using this wrapper. In my opinion Khronos should adopt Boost.Compute as their C++ layer for OpenCL. Boost.Compute provides compatibility with the OpenCL C interface through conversion operators that decay Boost.Compute types to their OpenCL C equivalents. This can be quite useful. On top of this wrapper Boost.Compute exhibits 3 core components: * types to interact with and issue commands to devices: these follow OpenCL concepts but are not necessary if defaults are used * means of managing memory (allocate, copy) on devices: this component contains also asynchronous operations which I consider essential in a library that deals with co-processors * a collection of parallel primitives and meta-functions with an STL interface: this components contains powerful iterators to combine containers and algorithms to implement more complex algorithms in an efficient manner One thing I'm not clear about is how asynchrony is handled. Command queues are exposed, issuing commands to different queues is a way to express concurrency. At the same time copy_async returns a future which is another way of exposing concurrency. It is out of the scope of Boost.Compute to solve the challenges of asynchronous/concurrent operations because it is a different and difficult topic not yet solved for C++ in general either, but at least the documentation should be more explicit about which commands are executed when, which commands are synchronous, which are asynchronous and what is the role of the command_queue in this regard. 2. What is your evaluation of the implementation? I did not evaluate the implementation in detail but looked at a few of the tricks Boost.Compute uses to generate kernels. The implementation of this part of the library is good and instructive. 3. What is your evaluation of the documentation? Boost.Compute documentation is of excellent quality. The recent addition of performance data is helpful. I could not find any documentation about fancy iterators, this should probably be added. Also, it would be great if the my questions regarding asynchrony/concurrency could be addressed in the documentation. 4. What is your evaluation of the potential usefulness of the library? Boost.Compute is extremely useful. With this library a developer familiar with the STL can utilize the processing power of GPUs without any knowledge of vector co-processor programming. The documentation shows that for large vector sizes, some Boost.Compute algorithms outperform the STL by an order of magnitude. 5. Did you try to use the library? With what compiler? Did you have any problems? I tried the unit-tests on a 8x GeForce Titan system without any problems and on a ARM Mali GPU with some unit tests failing. I'll be working with the library author to fix tcomp.lib.boost.develhe problems in these unit tests. I used gcc 4.8.2 for the tests on both GeForce and Mali. 6. How much effort did you put into your evaluation? A glance? Aquick reading? In-depth study? I reviewed the library a few months ago in-depth and reread the documentation for this review as well as ran some unit tests. 7. Are you knowledgeable about the problem domain? My job involves working with both CUDA and OpenCL. Furthermore I am the author of the Aura library [0] a similar, albeit lower level library for accelerator programming. 8. Do you think the library should be accepted as a Boost library? I think the library should be accepted into Boost. The interface is simple and easy to understand for non-experts and the benefits of using this library can be significant. I'd like to add that Boost.Compute represents one level of abstraction for accelerator programming. I'd like the Boost community to keep an open mind when it comes to different levels of abstraction, either lower (i.e. my Aura library) or higher (i.e. VexCL). Libraries with different levels of abstraction can coexist, be compatible with one another or could even build upon one another. Best Regards, Sebastian Schaetz [0] https://github.com/sschaetz/aura

2 1

File Handle and FILE* wrappers?
by Olaf van der Spek 16 Dec '14

16 Dec '14

Hi, Would there be any interest in wrappers for file handles / descriptors and FILE*? Sometimes one needs native handles or FILE* for interoperability or special features like memory mapped IO, but standard C++ doesn't provide convenient RAII friendly wrappers for these. The idea seems trivial yet quite useful. I'm aware of <boost/iostreams/device/file_descriptor.hpp> but it seems to be too high-level. I've put a simple start for FILE* at https://code.google.com/p/xbt/source/browse/trunk/xbt/misc/xbt/cfile.h What do you think? Also posted at https://groups.google.com/a/isocpp.org/forum/#!topic/std-proposals/Q4RdFSZg… -- Olaf

8 21

[utility] What happened to OptionalPointee/compare_pointees?
by Mostafa 16 Dec '14

16 Dec '14

1) OptionalPointee/compare_pointees reside here: libs/utility/OptionalPointee.html, but there's no way to navigate to it from here: libs/utility/ or here: libs/utility/utility.htm 2) IMO, compare_pointees should have stand alone documentation, and be grouped with pointee and indirect_reference. 3) pointee and indirect_reference are not iterator specific, therefore they shouldn't reside under iterator's documentation. IMO, compare_pointees, pointee and indirect_reference should all reside under a pointee utilities section. Thanks.

1 1

Spam ticket
by Barend Gehrels 15 Dec '14

15 Dec '14

Hi, This is not a spam-ticket but an annoying spam-comment in a long closed ticket. How can we handle this? Can the user of this comment (Smithg358) be blocked? Thanks, Barend -------- Original message -------- Onderwerp: Re: [Boost C++ Libraries] #6019: Convex hull and Area, combined, sometimes give wrong result Datum: Sat, 13 Dec 2014 23:23:53 -0000 Van: Boost C++ Libraries <noreply(a)lists.boost.org> CC: boost-bugs(a)lists.boost.org #6019: Convex hull and Area, combined, sometimes give wrong result ------------------------------------------+------------------------------ Reporter: Crispin Cooper <cooperch@…> | Owner: barendgehrels Type: Library Submissions | Status: reopened Milestone: Website 1.X | Component: xpressive Version: Boost.Build-M3 | Severity: Not Applicable Resolution: | Keywords: convex hull area ------------------------------------------+------------------------------ Changes (by Smithg358): * status: closed => reopened * severity: Problem => Not Applicable * type: Bugs => Library Submissions * component: geometry => xpressive * version: Boost 1.47.0 => Boost.Build-M3 * milestone: To Be Determined => Website 1.X * resolution: fixed => Comment: Your goal is to breed all the different dragons available to you ddgkbecefcfgddbk -- Ticket URL: <https://svn.boost.org/trac/boost/ticket/6019#comment:7> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.

2 2

[safe_numerics] questioning the basic idea
by Andrzej Krzemienski 15 Dec '14

15 Dec '14

Hi, I was going through the Safe Numerics library in Boost Library Incubator, and I realized I disagree with the basic idea it is built on. I wanted to rise my concerns here. If I were to summarize in one sentence what this library is, I would say: a drop-in replacement for type int that checks for overflow in run-time and throws an exception if it finds one. Did I get it right? The remainder of this post is based on this interpretation. If so, I am not sure if this idea is a good one and worth promoting in Boost. BTW this is one of my criteria for letting a library into Boost: whether it promotes worthy ideas. I agree with the statement that a program should be UB-free. But I do not think that the approach of letting the programmer do what he did before, having the library or some run-time tool check for potential UB, and throwing an exception instead makes the program any better (or safer). It is just hiding the symptoms but not curing the disease. The programmer should not plant the UB in the first place - I agree. But this is different than first doing the mess and then having the run-time clean it up for you. I know it works for many people, in a number of languages, and it may even be considered a practical solution, but (by inclusion into Boost) I wouldn't like to be sending the message "this is how you are suppose to code". I try to recall how I use type int. I do not think I ever use it for anything that would be close to "numeric" as I know the term from math. Use Case 1 (an index): for (size_t i = 0, I = v.size(); i != I; ++i) { if (i != 0) str += ","; str += v[i]; } There doesn't appear to be a good reason to wrap it into safe<int> here, even though the incrementation could possibly overflow. Plus, it would kill my performance. Use Case 2 (using reasonably small range): I used an int to represent a square on a chessboard. There is only 64 squares, so I couldn't possibly overflow, on whatever platform. And even if there exists a platform where 64 doesn't fit into an int, I would not use safe<int> there. I would rather go for something like double_int. If I were to use some numeric computations on integers and I perceived any risk that I may overflow, I would not be satisfied with having the computations stop because of an exception. I would rather use a bigger type (BigInt?). I do not think int is even meant to be used in numerical computations. I believe it is supposed to be a building block for building more useful types like BigInt. One good usage example I can think of is this. After a while of trying to chase a bug I comae up with a hypothesis that my int could be overflowing. I temporarily replace it with safe<int> and put a break point in function overflow() to trap it and support my hypothesis. I would probably use a configurable typedef then: #ifndef NDEBUG typedef safe<int> int_t; #else typedef int int_t; #endif But is this the intent? But perhaps it is just my narrow perspective. Can you give me a real-life example where substituting safe<int> for int has merit and is not controversial? I do not mean the code, just a story. Regards, &rzej

6 12

[endian] Heads up: breaking name changes coming
by Beman Dawes 15 Dec '14

15 Dec '14

Boost.Endian develop branch is about to have major changes merged in as part of the preparation for a mini-review. AFAICR, the breaking changes are limited to header, class, and function name changes, but there are a lot of hopefully non-breaking changes so I could easily be wrong about that. If you are currently using Boost.Endian develop branch, you will need to change your code accordingly. It would make sense to wait a few days until the mini-review merge is complete and any fixes required by regression test failures are fixed. Thanks for your patience, --Beman

1 0

Re: [boost] List of C++ 11 only Boost libraries and their status?
by Dave Gomboc 14 Dec '14

14 Dec '14

On Sat, Dec 13, 2014 at 08:37 AM, Rogerio dos Santos <rogerio.santos.main(a)gmail.com> wrote: > > On Sat, Dec 13, 2014 at 8:27 AM, Nat Goodspeed <nat(a)lindenlab.com> wrote: >> >> I'm just contradicting the assumption that those who must work with >> old compilers aren't doing any new development, or have no interest in >> new libraries. >> > > To add to this point, I would like to mention that even new developments > trends might require support to old or limited compilers. E.g.: IoT, real > time projects, industrial HMIs and mobile applications. > > Roger Indeed. I work on embedded, real-time industrial control systems in a field where certain specifications (unfortunately, IMO) severely restrict the platform choices available. In many cases, the systems developed must be built using pre-C++98 compiler technology. While that is a problem I am attempting to address, I suspect it is going to take at least another year to do so, and I am confident that at least one of the platforms will probably never support multi-threading even if its vendor does end up improving or replacing its toolchain (and I have no iron-clad guarantee from the vendor that the toolchain will actually be improved or replaced, though I have a reasonable hope). None of the above constraints imply that the libraries developed by Boost are not of use for these systems, or that we are not interested in using Boost libraries to the extent that it is possible to do so. I think it is possible to structure compatibility code so that it doesn't egregiously interfere with future development. I always get nervous when Steve posts asking to hack away the support for a few more of the older toolchains. While I fully appreciate that his end-goal is well-intentioned, there's still important code out there relying upon some of those pre-C++98 workarounds that can still benefit from the fixes and new libraries introduced into new versions of Boost. Consequently, I'm much in favour of allowing Boost library maintainers who wish to retain support for older compilers the latitude to do so. Dave

2 1

List of C++ 11 only Boost libraries and their status?
by Niall Douglas 13 Dec '14

13 Dec '14

For C++ Now 2015 I am intending to present an overview of C++ 11 only Boost libraries in the review queue or very near the review queue by the time of the conference. I'd appreciate help filling in missing gaps in this list: * Boost.Spirit X3 ETA to Boost review: unknown, last commit was June 2014. * Boost.Proto 0x ETA to Boost review: unknown, last commit was Oct 2013. * Boost.Hana ETA to Boost review: Summer 2015, last commit was today. * Boost.AFIO ETA to Boost review: Already in review queue, last commit was two days ago. * Boost.BindLib ETA to Boost review: Q1 2015, last commit was two days ago. * Boost.Spinlock ETA to Boost review: Q2 2015, last commit was four days ago. * Boost.KernelAlloc ETA to Boost review: Q1 2015, last commit was today. * Boost.Expected ETA to Boost review: no later than Summer 2015 probably much earlier, last commit was two weeks ago. * Boost.CRUX ETA to Boost review: hopefully by end of 2015, last commit was three days ago. I have to admit surprise at how long the list I have collected already is. Are there any other C++ 11 only Boost libraries I am missing, or have I got the ETAs wrong? Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

24 49

New Feature, MathString.
by Jakub trzciński 13 Dec '14

13 Dec '14

Hi. My name is Jacob and i am new here.i have idea for new feature in boost. Actually i write a little library whitch name MathString. As you see by name the library will be calcule Row's from string. But it's not all. I was write a interface which add own Mathematical functions for row and variables. If you accept my idea i will send whole code. Code for example MathString test("sqrt(x,2)"); test.LinkFunction(&sqrt,"sqrt"); test.pushVariable("x",4); cout<<test.getResluts(); This code will be return 2 (as you know root with level 2 of 4 equals 2)

3 2

C++ Concept-based tag dispatching using the Tick library
by pfultz2 13 Dec '14

13 Dec '14

Hello Everyone, For those interested. I added support for tag dispatching in the Tick. The reason it wasn't added earlier was concern over specialization. So now as a simple example, the `advance` function could be implemented like this: TICK_TRAIT(is_incrementable) { template<class T> auto requires_(T&& x) -> tick::valid< decltype(x++), decltype(++x) >; }; TICK_TRAIT(is_decrementable, is_incrementable<_>) { template<class T> auto requires_(T&& x) -> tick::valid< decltype(x--), decltype(--x) >; }; TICK_TRAIT(is_advanceable, is_decrementable<_>) { template<class T, class Number> auto requires_(T&& x, Number n) -> tick::valid< decltype(x += n) >; }; template<class Iterator> void advance_impl(Iterator& it, int n, tick::tag<is_advanceable>) { it += n; } template<class Iterator> void advance_impl(Iterator& it, int n, tick::tag<is_decrementable>) { if (n > 0) while (n--) ++it; else { n *= -1; while (n--) --it; } } template<class Iterator> void advance_impl(Iterator& it, int n, tick::tag<is_incrementable>) { while (n--) ++it; } template<class Iterator> void advance(Iterator& it, int n) { advance_impl(it, n, tick::most_refined<is_advanceable<Iterator>>()); } Now, specialization is still supported in a sane way. As an example, say there was an iterator called `foo_iterator` that fulfilled the type requirements for `is_incrementable`, `is_decrementable`, and `is_advanceable`, but it had an incorrect `+=` operator on it(perhaps it crahsed at runtime). So `is_advanceable` can be specialized to prevent this problem: template<> struct is_advanceable<foo_iterator> : std::false_type {}; Even though it is specialized to false, it can still dispatch to `tag<is_decrementable>` and `tag<is_incrementable>` tags. You can read more about it here: http://pfultz2.github.io/Tick/doc/html/tag/ Any feedback is appreciated. Thanks, Paul Fultz II -- View this message in context: http://boost.2283326.n4.nabble.com/C-Concept-based-tag-dispatching-using-th… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

Duration of formal reviews
by Vladimir Prus 12 Dec '14

12 Dec '14

Some time ago we had a poll about formal reviews problems: https://plus.google.com/u/0/+VladimirPrus/posts/5spgjicc3fv The majority said that ten days are not enough. Of course, it's not very statistically significant, but that's the only data we've got, and we have a rather sparse schedule. How about trying two weeks for a formal review? Thanks, -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com

4 3

Is Boost.Xpressive's sregex::compile() thread-safe for an object only used in that thread?
by Chambers, Matthew 12 Dec '14

12 Dec '14

I have a case where I am compiling a dynamic regex based on client code input, and it works except for when I run my multi-threaded unit test 100-1000 times. When I run it with 1 thread, it never fails. When I run it with 2 or 4 threads it fails at this rare frequency. Except on my build server, where it seems to fail most of the time, which is how I learned about the issue to begin with. It's not crashing though, it's just very rarely returning the wrong results, and not always in the same place in the unit test. So I'm trying to understand Xpressive's thread safety. I understand it as far as not using a regex object in multiple threads until it's finished compiling and not sharing a match_results across threads, but what about compiling different regex objects for each thread: if two threads are compiling two different regexes (or even the same const regex string but from different threads, which is possible with my test code), is that ok? I'm seeing this failure on MSVC 12 but I think I also got it with VC10, just not as reliably on the build server (but the build server had to be upgraded to Windows 2012 to install VC12, so maybe that OS change had an effect as well). Thanks, -Matt

2 2

[coroutine] x86 msvc11 stack corruption
by Tobias Loew 12 Dec '14

12 Dec '14

Hi, I use Boost 1.55 uni-directional coroutines to build an x86 MSVC11 application. I have a simple pull-type (boost::coroutines::coroutine<void>::pull_type) that under certain reproducable conditions destroys the stack after returning from the coroutine. Here is the corrupted stack as shown by VS2012 > ebs2000.exe!CScriptMainFrame::DoRun(CPascalEditorDoc * 0x00000000, int 0x00000000, int 0x00000000) Line 3372 C++ ebs2000.exe!CScriptMainFrame::OnDebugStepover() Line 4916 C++ mfc110u.dll!_AfxDispatchCmdMsg(CCmdTarget *, unsigned int, int, void (void) *, void *, unsigned int, AFX_CMDHANDLERINFO *) C++ 00000002() Unknown [Frames below may be incorrect and/or missing] mfc110u.dll!CCmdTarget::OnCmdMsg(unsigned int, int 0x00000000, void *, AFX_CMDHANDLERINFO *) Line 364 C++ mfc110u.dll!CWnd::OnCommand(unsigned int 0x00018263, long 0x00000000) Line 2785 C++ mfc110u.dll!CFrameWnd::OnCommand(unsigned int 0x00018263, long 0x00000000) Line 389 C++ ... This only happens in windows x86 32-bit release-builds when the coroutine finishes upon a user-action that also includes a windows WM_SETFOCUS message on my menu-bar. If at least one of the following is true, the stack-corruption does NOT happen: - debug-build - x64 build - using a different pull-type, e.g. enum status_enum{...}; boost::coroutines::coroutine<status_enum>::pull_type - not returning form the coroutine, but pushing just before the end of the coroutine and swapping the pull-type-variable with a default constructed "not-a-coroutine" Even though I have a lot of workarounds, I still would like to know, why this happens. regards Tobias PS: I had to recompile ml /safeseh /c make_i386_ms_pe_masm.asm ml /safeseh /c jump_i386_ms_pe_masm.asm to get SAFESEH-libraries. -- View this message in context: http://boost.2283326.n4.nabble.com/coroutine-x86-msvc11-stack-corruption-tp… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 3

[review] Last day for formal review for Sort library
by Edward Diener 12 Dec '14

12 Dec '14

Today is the last day for the formal review of the Sort library by Steven Ross, which started November 10. We have had some great discussions and reviews so far and I would like to thank everybody involved, but as always we need more formal reviews. If you need any delay for your review after today, please contact me at 'eldiener at tropicsoft dot com' and I will take your review into account if given within a reasonable period of time after today. About the Sort library ================== The Sort library is a library which implements hybrid sorting algorithms based on a Spreadsort ( http://en.wikipedia.org/wiki/Spreadsort ), of which the author of the library, Steven Ross, is the inventor. The algorithm provides a sort that is faster than O(n*log(n)). The library provides a generic implementation of high-speed sorting algorithms that outperform those in the C++ standard in both average and worst case performance. These algorithms only work on random access iterators. They are hybrids using both radix and comparison-based sorting, specialized to sorting common data types, such as integers, floats, and strings. These algorithms are encoded in a generic fashion and accept functors, enabling them to sort any object that can be processed like these basic data types. Where to get it =============== The library is available on github at https://github.com/spreadsort/sort. The library is in modular Boost format and can be cloned to libs/sort under your local modular boost directory. I have provided as the review manager online documentation at: http://eldiener.github.io/sort Review guidelines ================= Reviews should be submitted to the developer list (boost(a)lists.boost.org) preferably with '[sort]' in the subject. Or if you don't wish to for some reason or are not subscribed to the developer list you can send them privately to me at 'eldiener at tropicsoft dot com'. If so, please let me know whether or not you'd like your review to be forwarded to the list. For your review you may wish to consider the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should attempt to answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Even if you do not wish to give a full review any technical comment regarding the library is welcome as part of the review period and will help me as the review manager decide whether the library should be accepted as a Boost library. Any questions about the use of the library are also welcome.

6 11

Help test MSVC 14 CTP compiler
by Andrzej Krzemienski 11 Dec '14

11 Dec '14

Hi Everyone, I am trying to determine the root cause of the failure in one of Boost.Optional regression tests. Namely: http://www.boost.org/development/tests/develop/developer/output/teeks99-08f… Could anyone with the access to MSVC 14 CTP compiler check if the following code compiles? // BEGIN CODE #include <boost/static_assert.hpp> #include <boost/type_traits/is_nothrow_move_assignable.hpp> struct NothrowCtor { NothrowCtor(NothrowCtor&&) BOOST_NOEXCEPT_IF(true) {}; void operator=(NothrowCtor&&) BOOST_NOEXCEPT_IF(false) {}; }; BOOST_STATIC_ASSERT(!::boost::is_nothrow_move_assignable<NothrowCtor>::value); int main() {} // END CODE Regards, &rzej

5 13

Use of boost in safety critical work
by Andrew Marlow 11 Dec '14

11 Dec '14

Hello fellow boosters, I am currently considering a job which involves embedded safety critical. It is for a neonatal ventilator so the safety critical aspect really is critical rather than just 'jolly important'. The company says the development will be in C++ but they have not even heard of boost, let alone use it. They introduced me to a new acronym, well new to me anyway: SOUP. It stands for Software of Unknown Pedigree. They classify boost as SOUP. I have used boost before in embedded work but I have never done safety critical work before so I don't know how widely boost is used there. Can anyone who *has* worked on safety critical stuff comment please? -- Regards, Andrew Marlow http://www.andrewpetermarlow.co.uk

16 26

Re: [boost] [asio] Is Boost.Asio ported for Windows Runtime?
by Moshe Rubin 11 Dec '14

11 Dec '14

Hi Rob, The reason I posted an Asio-related question to this forum is because the Asio mailing list is all but dead. In October there were three (3) posts in all, in November zero posts, and this December only one post - mine. Sounds dead to me. Moshe >> On December 9, 2014 3:11:32 AM EST, Moshe Rubin <moshe(a)hyperlync.com> wrote: >> [snip] >>Can the Boost.Asio maintainer, or anyone else, verify if Boost.Asio can >>be built as-is for WinRT, or does it need to be ported? > I added "[asio]" to the subject to help attract the right audience, but you probably want the Asio mailing list for such a question: http://think-async.com/Asio/MailingList.

2 1

Re: [boost] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Moshe Rubin 11 Dec '14

11 Dec '14

Oliver, I forgot to mention that stack_traits.cpp has a typo: it should include: #include <boost/context/stack_context.hpp> rather than #include <boost/econtext/stack_context.hpp> (note the extra 'e') Moshe -------------------- > > I'm currently attempting to port libraries for Windows Phone 8.1 and have not started concentrating on the units tests (of course. Can you please educate me on how to run the boost.context units tests? > > compile the code in directory <boost>/libs/context/test and execute the binaries on WindowsPhone, please (remove untested.cpp in > build/Jamfile.v2) Oliver, I was able to compile and run the context test as a regular Windows app (i.e., not Windows Phone). Here are the results I got: C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi>test_context.exe Running 9 test cases... f1: entered *** No errors detected Detected memory leaks! Dumping objects -> {478} normal block at 0x00530470, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {477} normal block at 0x00520440, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {473} normal block at 0x0051E3B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {469} normal block at 0x0050E320, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {465} normal block at 0x0050C290, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {461} normal block at 0x0050A200, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {457} normal block at 0x00508170, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {453} normal block at 0x005060E0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {449} normal block at 0x005040B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {445} normal block at 0x00502080, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD Object dump complete. C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi> It is not clear to me how to compile and run the context test on a Windows Phone. Windows Phone does not run regular executables, so a GUI client app would need to be written. It is not clear to me how to run the test for Windows Phone (I doubt the Boost.Test framework supports a Windows Phone interface). Please advise Moshe

1 0

Re: [boost] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Moshe Rubin 11 Dec '14

11 Dec '14

> > I'm currently attempting to port libraries for Windows Phone 8.1 and have not started concentrating on the units tests (of course. Can you please educate me on how to run the boost.context units tests? > > compile the code in directory <boost>/libs/context/test and execute the binaries on WindowsPhone, please (remove untested.cpp in > build/Jamfile.v2) Oliver, I was able to compile and run the context test as a regular Windows app (i.e., not Windows Phone). Here are the results I got: C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi>test_context.exe Running 9 test cases... f1: entered *** No errors detected Detected memory leaks! Dumping objects -> {478} normal block at 0x00530470, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {477} normal block at 0x00520440, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {473} normal block at 0x0051E3B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {469} normal block at 0x0050E320, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {465} normal block at 0x0050C290, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {461} normal block at 0x0050A200, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {457} normal block at 0x00508170, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {453} normal block at 0x005060E0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {449} normal block at 0x005040B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {445} normal block at 0x00502080, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD Object dump complete. C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi> It is not clear to me how to compile and run the context test on a Windows Phone. Windows Phone does not run regular executables, so a GUI client app would need to be written. It is not clear to me how to run the test for Windows Phone (I doubt the Boost.Test framework supports a Windows Phone interface). Please advise Moshe

2 1

Re: [boost] Develop Tests Failing Again
by Tom Kent 11 Dec '14

11 Dec '14

On Mon, Dec 8, 2014 at 1:04 PM, Tom Kent <lists(a)teeks99.com> wrote: > It looks like my windows and linux tests have been failing since last > saturday, around 4pm pacific time. > > The end of results/bjam.log is as follows: > boost-test(RUN) "serialization/test_helper_support_xml_warchive" : > "libs/serialization/test/test_ > helper_support.cpp" > error: at D:/local/teeks99-08/a/boost_bb/src/kernel\modules.jam:107 > error: Unable to find file or target named > error: 'test_interrupts.cpp' > error: referred to from project at > error: '../libs/serialization/test' > > Tom > Apparently it is fixed now. Anyone know what happened, I didn't see any messages about it. Tom

2 1

Re: [boost] [Boost-build] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Jürgen Hunold 10 Dec '14

10 Dec '14

Hi Volodya, Am Freitag, 5. Dezember 2014, 11:19:25 schrieb Vladimir Prus: > On 12/04/2014 09:37 PM, Jürgen Hunold wrote: > > Since sometime last week, Boost.Context depends on Boost.System. > > Unfortunately, Boost.Context has to explicitly calculate the > > <address-model> and <architecture> properties in order to select the > > assembler needed, as those properties have no default value (yet). > > It so happens that Boost.System is once requested without those properties > > and a second time with them. And the <layout> rule is asked to build both > > target with the same effective name in stage/lib. => clash. > > > > So explicitly specifying the properties leads to the right solution. > > > > I cross-mail this to the Boost.Build list to see if someone has a > > solution. > > It would seem I'd have to make architecture and address-model always set, > possibly by lifting current boost.context code for same to the top level? > At least I don't see any other plausible soluton. Me neither. And I think this is not the only configuration code that needs uplifting. We have some duplicated configuration code for ICU and zlib. The main difficulty is the question of sensible default feature values for <address-model> and <architecture>. Especially for Windows with its path length limitations. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

1 0

Review request for Compute
by Antony Polukhin 10 Dec '14

10 Dec '14

Hi, Please add the the Compute library to the review schedule. Compute is a GPU/parallel-computing library for C++ based on OpenCL. Author: Kyle Lutz Source code: https://github.com/kylelutz/compute Documentation: http://kylelutz.github.io/compute/ Review Manager: Antony Polukhin Approximate review date: end of November - December 2014 -- Best regards, Antony Polukhin

2 2

Re: [boost] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Moshe Rubin 10 Dec '14

10 Dec '14

Oliver, I'm currently attempting to port libraries for Windows Phone 8.1 and have not started concentrating on the units tests (of course. Can you please educate me on how to run the boost.context units tests? Moshe > Hello Moshe, > could you tell me if boost.context passes its unit-tests on > Windows-Phone, please? > thx, > Oliver > > 2014-12-09 9:40 GMT+01:00 Moshe Rubin <moshe(a)hyperlync.com<mailto:moshe@hyperlync.com>>: > > A belated "thank you" to Juergen Hunold and Oliver Kowalke for their help in solving the problem. Indeed, when "address-model=32" was added to the command line it solved the problem and enabled me to build all the Windows Phone ARM libraries in one fell swoop. > > > > Thanks very much, > > > > Moshe

2 1

[iterators] Missing typedefs in v1.57
by news.gmane.org 10 Dec '14

10 Dec '14

I posted this a week ago in the user mailing list but it went unnoticed. Perhaps this developers' list is a better place to post it. The typedefs for difference_type and reference used to be in scope for classes derived from iterator_facade. Since v1.57 they have to be declared thus: typedef typename iterator_facade_::difference_type difference_type; typedef typename iterator_facade_::reference reference; This seems out of place for a class that was designed to reduce boiler plate code. However, if the change was intentional, please document it. Thanks, Keith MacDonald

3 5

[documentation] Are SVG's in documentation viable now?
by John Maddock 10 Dec '14

10 Dec '14

Folks I need your opinions, Since it's inception, Boost.Math has used PNG versions of equations and graphs even though scalable SVG versions have been available. Unfortunately, a variety of issues have prevented their use. Fortunately, the logjam now appears to have cleared, and use of SVG's appears viable. So... I wonder if I can get folks to point their browsers at http://jzmaddock.github.io/doctest/html/svg_test/equations.html and let me know if there are any issues? One that I'm aware of, is that the equations reference Window's specific fonts, but so far in my tests this appears not to be an issue. Many thanks, John. PS, I'm aware of MathJax and similar solutions for equations - but these generate so many security warnings on IE when used in local docs (not on a server), that it's a non-starter for now. Besides, we have the SVG's already, and it's a one line change to make use of them ;-)

13 22