March 2014 - Boost - lists.preview.boost.org

Boost.odeint Applicant Test
by Zeshawn Shaheen 16 Mar '14

16 Mar '14

Hi, I am Zeshawn Shaheen, a junior at the University of the Pacific in Stockton, CA, US. I am a double major in computer science and mathematics and was interested in partaking in developing implicit routines for Boost.odeint. I've read in the Boost Developers Archive that a small test is given regarding the applicant's coding skills and the odeint library. I would appreciate it if I could be given the test. Thank you. Sincerely, Zeshawn Shaheen

1 0

[GSoC 2014] [Computation of generalized hypergeometric functions]
by Cosmin Boaca 16 Mar '14

16 Mar '14

Hello, I am Cosmin Boaca, and I want to contribute to boost during GSoC 2014. Here is my proposal [0] . Please give me some feedback about it. [0] https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014… Thank you, Cosmin Boaca

4 6

Re: [boost] [GSoC] Boost.Thread executors proposal
by Ian Forbes 15 Mar '14

15 Mar '14

>First provide in addition a static polymorphic interface. The template >functions submit_at and submit_after would accept any chrono >`time_point` and `duration`. Is this with respect to the granularity of the time point? e.g. nano/micro/mille etc? If it is I'm assuming this would take an executor and then convert the time point to the desired granularity (nanoseconds by default) then add it to the executor. >Second, provide an adaptor that wraps an scheduled executor and makes it >a polymorphic one. Polymorphic with respect to what? >Third, provide an adaptor that wraps an executor, manage the time based >operations using a specific thread and forward all the operations to the >wrapped executor. So this would take a reference to an executor or a shared_ptr then spawn a single thread that would loop and add the submitted closures at the desired time to the given executor? Ian, ________________________________________ From: Boost [boost-bounces(a)lists.boost.org] on behalf of Vicente J. Botet Escriba [vicente.botet(a)wanadoo.fr] Sent: Friday, March 14, 2014 3:34 AM To: boost(a)lists.boost.org Subject: Re: [boost] [Boost.Thread][GSoC] Boost.Thread executors proposal Le 13/03/14 04:59, Ian Forbes a écrit : > Hi, > > Here is my GSoC proposal for working on the scheduled executors classes. It can be found here: www.cs.mcgill.ca/~iforbe/ > > This proposal mainly deals with the implementation of classes extending the `scheduled_executor` interface. I have already written thread pool implementations with very similar functionality to the ones proposed. > > I feel that the current proposal could use a little bit of touching up so please feel free to leave comments/criticisms. > > I would also be willing to take on any other work related to executors such the the dynamic/work-stealing thread pool implementation or the parallel algorithms library and add it into my proposal. > > Hi, I like your proposal on scheduled_executor and possibly extend it to a priority thread pool. I would let the work-stealing outside the proposal. Just to note that the closure would not be a std::function<void()> as this class doesn't accept a movable only function. Boost.Thread would include (version 1.56) a boost::executors::work as a type-erased class for closures. I'm looking for a different approach respect to scheduled work of the N3785 proposal. First provide in addition a static polymorphic interface. The template functions submit_at and submit_after would accept any chrono `time_point` and `duration`. Second, provide an adaptor that wraps an scheduled executor and makes it a polymorphic one. Third, provide an adaptor that wraps an executor, manage the time based operations using a specific thread and forward all the operations to the wrapped executor. What do you think of this approach? Best, Vicente _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Re: [boost] [GSoC] pipelines questions
by Thaler Benedek 14 Mar '14

14 Mar '14

> I'm interested in the Boost.Pipelines proposal of GSoC 2014. [snip] Hi, I created a preview [0] with a working example. Please see the readme file and example/hello.cpp. This demo does not have parallel abilities and supports only 1-to-1 transformations in the pipeline. The purpose of this is to showcase my programming abilities and ask your opinions regarding the design and implementation. I intend to have this repository as a supplement of my proposal. Thanks, Benedek [0]: https://github.com/erenon/pipeline

3 7

Permissions in boost::iostreams::mapped_file output
by Patrick Reynolds 14 Mar '14

14 Mar '14

Boost folks, Working with mapped_files in a project, I recently discovered that the files were being written to disk with unexpected permissions on the linux systems. I discussed this further in a pull request here: https://github.com/boostorg/iostreams/pull/2 Is this the proper avenue for making such a contribution? If not, where can I go to get started. Thanks, Patrick

1 1

[modular-boost] Errors on submodule update
by Marcel Raad 14 Mar '14

14 Mar '14

Hi, I'm using TortoiseGit 1.8.7 with msysgit 1.8.5.2 on Windows and have checked out the develop branch of the boost repository. On every submodule update, I get the following errors. Is the submodule configuration corrupt? Git seems to believe that there are msm and polygon submodules which are not in the libs directory: ... git.exe submodule update -- "libs/msm" ... git.exe submodule update -- "libs/polygon" ... git.exe submodule update -- "msm" error: pathspec 'msm' did not match any file(s) known to git. Did you forget to 'git add'? git.exe submodule update -- "polygon" error: pathspec 'polygon' did not match any file(s) known to git. Did you forget to 'git add'? ...

1 0

[Boost.Thread][GSoC] Boost.Thread executors proposal
by Ian Forbes 14 Mar '14

14 Mar '14

Hi, Here is my GSoC proposal for working on the scheduled executors classes. It can be found here: www.cs.mcgill.ca/~iforbe/ This proposal mainly deals with the implementation of classes extending the `scheduled_executor` interface. I have already written thread pool implementations with very similar functionality to the ones proposed. I feel that the current proposal could use a little bit of touching up so please feel free to leave comments/criticisms. I would also be willing to take on any other work related to executors such the the dynamic/work-stealing thread pool implementation or the parallel algorithms library and add it into my proposal. Thank, Ian

3 2

[GSoC] [RFC] Proposal: A C++11 enabled TMP library
by Louis Dionne 14 Mar '14

14 Mar '14

Hi, As suggested earlier on this list, I am posting my GSoC proposal here in an attempt to gather comments and to improve the proposal. Basically, if you would not give the proposal 10/10, then I would like to know the reason so I can change it accordingly. I am strongly motivated with this project and I want to maximize my chances of getting in. The proposal is written in Markdown because that's easier to read than plain text; it is available here (secret gists are just hidden from search engines): http://gist.github.com/ldionne/d05528280db79105e30d Please post all constructive comments that come to your mind. Thank you, Louis Dionne

2 8

GSoC Proposal for Boost.numeric.uBLAS (Review Request)
by Ganesh Prasad 13 Mar '14

13 Mar '14

Hi I have tried to write a feasible proposal for uBLAS, but I am not exactly sure about the time line I have proposed. I have considered my own efficiency and estimated the time considering the dependencies among the proposed algorithms. I will be glad to receive some advice regarding this project. Best Wishes Ganesh Prasad

1 0

[atomic] gcc-atomic.hpp errors with Clang 3.4
by Richard Hadsell 12 Mar '14

12 Mar '14

I am trying to build Boost 1.55 libraries with Clang 3.4 using g++ 4.8.2 as the toolchain on CentOS 6.5. I think these errors arise from trying to initialize 128-bit integers with 0: clang-linux.compile.c++.without-pth bin.v2/libs/atomic/build/clang-linux-3.4/release/address-model-64/instruction-set-core2/link-static/threading-multi/lockpool.o In file included from libs/atomic/src/lockpool.cpp:3: In file included from ./boost/atomic.hpp:12: In file included from ./boost/atomic/atomic.hpp:17: In file included from ./boost/atomic/detail/platform.hpp:22: ./boost/atomic/detail/gcc-atomic.hpp:961:64: error: no matching constructor for initialization of 'storage_type' (aka 'boost::atomics::detail::storage128_type') explicit base_atomic(value_type const& v) BOOST_NOEXCEPT : v_(0) ^ ~ ./boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'int' to 'const boost::atomics::detail::storage128_type' for 1st argument struct BOOST_ALIGNMENT(16) storage128_type ^ ./boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate constructor (the implicit default constructor) not viable: requires 0 arguments, but 1 was provided ./boost/atomic/detail/gcc-atomic.hpp:968:22: error: no viable conversion from 'int' to 'storage_type' (aka 'boost::atomics::detail::storage128_type') storage_type tmp = 0; ^ ~ ./boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'int' to 'const boost::atomics::detail::storage128_type &' for 1st argument struct BOOST_ALIGNMENT(16) storage128_type ^ Similar errors follow these. I think the initializations to 0 are superfluous, because they are followed by memcpy calls that overwrite them. I will try that fix myself, but I am looking for an official fix that will get into the next release. -- Dick Hadsell 203-992-6320 Fax: 203-992-6001 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studioshttp://www.blueskystudios.com 1 American Lane, Greenwich, CT 06831-2560 Follow Blue Sky Studios on Facebook <http://www.facebook.com/BlueSkyStudios> and Twitter <http://twitter.com/#%21/blueskystudios>

2 1