Deprecate, warn and convert seems reasonable. But for how long ?
As the number of automatic conversions OMPI supports has shown a tendency
to increase, and as these conversions happen all over the code base, we
might want to setup a well defined path to deprecation, what and when has
been deprecat
On Apr 8, 2020, at 9:51 AM, Ralph Castain via devel
wrote:
>
> We have deprecated a number of cmd line options (e.g., bynode, npernode,
> npersocket) - what do we want to do about their MPI_Info equivalents when
> calling comm_spawn?
>
> Do I silently convert them? Should we output a deprecat
We have deprecated a number of cmd line options (e.g., bynode, npernode,
npersocket) - what do we want to do about their MPI_Info equivalents when
calling comm_spawn?
Do I silently convert them? Should we output a deprecation warning? Return an
error?
Ralph
Thanks George,
I'll try to search for those examples through the mailing list messages.
I suspect it is not going to be easy to find them though.
Regards,
Luis
On 07/04/2020 22:29, George Bosilca via devel wrote:
All the collective decisions are done on the first collective on each
communica
