On 4/26/2016 9:01 PM, Belcourt, Kenneth wrote:
On Apr 26, 2016, at 11:47 AM, Rene Rivera
wrote: On Tue, Apr 26, 2016 at 3:36 AM, alainm
wrote: On 25/04/2016 21:12, Rene Rivera wrote:
On Mon, Apr 25, 2016 at 2:05 PM, Belcourt, Kenneth
wrote: On Apr 25, 2016, at 12:08 PM, Vladimir Prus
wrote:
On 4/23/2016 10:02 PM, Belcourt, Kenneth wrote:
> It’d be nice if serialization worked with MPI for the release, though > I’m not sure it’s a show stopper.
What is the actual impact of this problem? E.g. which percentage of MPI
users will find their code
no longer compiling?
Fair question, no idea really. I know that Boost MPI's used on multiple projects where I work, though it’s easy enough for us to just skip using the 1.61 release to avoid breaking our MPI serialization code.
Sorry if my ignorance of how MPI shows :-) .. How much of MPI is usable with this problem? Is it usable at all? Is it partially usable?
No part of Boost MPI is usable, meaning no code built on top of Boost.MPI will compile.
Just tried.
Thanks for the info.. But given that we don't have *any* test results with MPI passing (i.e. nothing on develop yet).. I'm afraid it's going to stay broken this release.
I just applied a patch that should get all of graph, graph_parallel, and MPI passing on develop. Tomorrow should be clean, if you can wait that long.
The most recent results for MPI are from April 20, are you sure we'll have any results tomorrow? What about graph and graph_parallel? Are they also broken in current master? -- Vladimir Prus http://vladimirprus.com