Hi
The Cartesian decomposition part of the MPI spec does not seems to be
present in boost mpi.
Is it just due to a lack of resources or is it useless for some reason ?
I'd like to look into it but would like to make sure there is a point.
Best regards
Alain
I have 3 pull requests related with those issues.
The mpi test do not hang anymore with Intel's MPI with those.
Thanks,
Alain
On 08/09/2014 18:14, Alain Miniussi wrote:
Hi,
I have an issue with that test that goes into an infinite loop.
I am using intel MPI 4.1.3 on a linux box.
I did run
Hi,
I have a few small pull request on the develop branch that have been
pending for a few days and was wondering what was the usual
process/delay one can expect. Is the pull request automatically notified
to potential mergers ? Should I file a ticket on the tracker ?
Thanks!
Alain
Message -
From: Alain Miniussi alain.miniu...@oca.eu
To: boost-mpi@lists.boost.org
Sent: Wednesday, September 3, 2014 3:44:03 AM
Subject: [Boost-mpi] cartesian ecomposion
Hi
The Cartesian decomposition part of the MPI spec does not seems to be
present in boost mpi.
Is it just due to a lack
Hi all.
I have a question regarding:
https://github.com/boostorg/mpi/compare/master...develop
I guess that all the commit, specially the pull requests, listed are
those that made their way to develop but not to master.
What is the protocol/usage for having the stuff on the develop branch
merge
https://github.com/boostorg/mpi/pull/49
On 15/07/2017 14:05, Alain Miniussi via Boost-mpi wrote:
Hi,
I just realized that people with a platform boost installed had their
1.64 distrib building for the wrong reasons... (as long as a "correct"
get_data is included, it can come
I answered on the patch issue in another post.
Regarding the todo list:
On 15/07/2017 00:01, MM wrote:
[..]
Dream wishes for boost mpi are extension to support MPI3-1, for
c++11/14 if applicable, clearer documentation in terms of optimization
of mpi datatypes, and usage of serialization lib.
It passes with:
- Intel compiler 17.0.2
- library IMPI 5.0.3.048
On 15/07/2017 14:08, Alain Miniussi via Boost-mpi wrote:
https://github.com/boostorg/mpi/pull/49
On 15/07/2017 14:05, Alain Miniussi via Boost-mpi wrote:
Hi,
I just realized that people with a platform boost
Hi Noel,
On 17/07/2017 03:11, Belcourt, Kenneth wrote:
Hi Alain,
On Jul 15, 2017, at 7:28 AM, Alain Miniussi via Boost-mpi
<boost-mpi@lists.boost.org <mailto:boost-mpi@lists.boost.org>> wrote:
It passes with:
- Intel compiler 17.0.2
- library IMPI 5.0.3.048
O
Hi,
Has anyone ever used the python bindings ?
How should we run the associated test ?
Thanks
Alain
___
Boost-mpi mailing list
Boost-mpi@lists.boost.org
https://lists.boost.org/mailman/listinfo.cgi/boost-mpi
I merged it to master, let me know of any issue.
Thanks
Alain
On 15/07/2017 15:28, Alain Miniussi via Boost-mpi wrote:
It passes with:
- Intel compiler 17.0.2
- library IMPI 5.0.3.048
On 15/07/2017 14:08, Alain Miniussi via Boost-mpi wrote:
https://github.com/boostorg
On 22/07/2017 22:11, Belcourt, Kenneth wrote:
On Jul 20, 2017, at 4:02 PM, Alain Miniussi via Boost-mpi
<boost-mpi@lists.boost.org> wrote:
Unless I'm missing something (been a long time), the current diff between
develop and master mostly consist of:
- the cartesian communicators.
On 23/07/2017 00:41, Alain Miniussi via Boost-mpi wrote:
On 22/07/2017 22:11, Belcourt, Kenneth wrote:
I see that your recent changes have now broken develop for
clang-linux-3.8.1, and gcc-4.7.2. So I guess Boost is dropping support
for gcc-4.7.x, or was that unintentional on your part
On 23/07/2017 08:35, Alain Miniussi wrote:
On 23/07/2017 05:09, Belcourt, Kenneth wrote:
On Jul 22, 2017, at 5:12 PM, Alain Miniussi <alain.miniu...@oca.eu
<mailto:alain.miniu...@oca.eu>> wrote:
On 23/07/2017 00:41, Alain Miniussi via Boost-mpi wrote:
On 22/07/2017 22:11, Belco
On 23/07/2017 05:09, Belcourt, Kenneth wrote:
On Jul 22, 2017, at 5:12 PM, Alain Miniussi <alain.miniu...@oca.eu
<mailto:alain.miniu...@oca.eu>> wrote:
On 23/07/2017 00:41, Alain Miniussi via Boost-mpi wrote:
On 22/07/2017 22:11, Belcourt, Kenneth wrote: I see that your recent
On 24/07/2017 05:29, Belcourt, Kenneth wrote:
On Jul 23, 2017, at 2:24 AM, Alain Miniussi <alain.miniu...@oca.eu
<mailto:alain.miniu...@oca.eu>> wrote:
On 23/07/2017 08:35, Alain Miniussi wrote:
On 23/07/2017 05:09, Belcourt, Kenneth wrote:
On Jul 22, 2017, at 5:12 PM, Al
On 24/07/2017 09:56, Alain Miniussi via Boost-mpi wrote:
On 24/07/2017 05:29, Belcourt, Kenneth wrote:
On Jul 23, 2017, at 2:24 AM, Alain Miniussi <alain.miniu...@oca.eu
<mailto:alain.miniu...@oca.eu>> wrote:
On 23/07/2017 08:35, Alain Miniussi wrote:
On 23/07/2017 05:
On 24/07/2017 10:12, Alain Miniussi via Boost-mpi wrote:
On 24/07/2017 09:56, Alain Miniussi via Boost-mpi wrote:
On 24/07/2017 05:29, Belcourt, Kenneth wrote:
Looks like different issues now:
gcc.compile.c++
../../../bin.v2/libs/mpi/build/gcc-4.7.2/debug/threading-multi/point_to_point.o
e doing so with so many differences between develop
and master).
I'm oky with both (as long as the merge in made relatively quickly so we
can move on) with a slight preference for keeping 1.65 a bug fix release.
Regards,
Alain
On 15/07/2017 14:08, Alain Miniussi via Boost-mpi wro
HI,
Not on my test platforms, but the warning is justified.
Could you file an issue that I can reference it i the fix.
Thanks
ALain
On 08/04/2018 18:31, Belcourt, Kenneth via Boost-mpi wrote:
Hi,
Hit this error with clang on Mac. Anyone else see this?
In file included from
Although I just realize I, for one, cannot submit issues agasint
boost-mpi, am I the only one in this situation ?
I the meantime I'll just go with a PL.
Thanks
Alain
On 08/04/2018 18:59, Alain Miniussi via Boost-mpi wrote:
HI,
Not on my test platforms, but the warning is justified.
Could
Hi
This is https://github.com/boostorg/mpi/pull/57, ican you have a look at
it ?
Thanks
On 08/04/2018 18:31, Belcourt, Kenneth via Boost-mpi wrote:
Hi,
Hit this error with clang on Mac. Anyone else see this?
In file included from libs/mpi/src/cartesian_communicator.cpp:12:
22 matches
Mail list logo
