[mpich-discuss] MPI_Address()
Michael Blocksome
blocksom at us.ibm.com
Wed Mar 12 11:38:17 CDT 2014
Would it be possible to make the inclusion of deprecated/deleted functions
in the mpi.h header configurable?
If so, then a "strict" mpich library could be configured, compiled, and
used to aid those who wish to port legacy applications to the new
standard. By default, this "strict" mode would be disabled in order to
preserve the current design decision.
Michael Blocksome
Parallel Environment MPI Middleware Team Lead, TCEM
POWER, x86, and Blue Gene HPC Messaging
blocksom at us.ibm.com
From: Rajeev Thakur <thakur at mcs.anl.gov>
To: <discuss at mpich.org>,
Date: 03/11/2014 09:51 PM
Subject: Re: [mpich-discuss] MPI_Address()
Sent by: discuss-bounces at mpich.org
There are a whole bunch of such functions that were deprecated in MPI 2.0
(in 1997) and removed in MPI 3.0 (in 2012). We discussed whether to keep
or remove them in MPICH, and decided to keep them so as not to
gratuitously break user codes that still use the old functions.
Rajeev
On Mar 11, 2014, at 9:28 PM, Orion Poplawski <orion at cora.nwra.com>
wrote:
> MPI_Address() was removed from the MPI API in the MPI-3 specification so
> it should be removed from mpich's mpi.h as well. Still present in 3.1
> and current repository.
>
> - Orion
>
> --
> Orion Poplawski
> Technical Manager 303-415-9701 x222
> NWRA/CoRA Division FAX: 303-415-9702
> 3380 Mitchell Lane orion at cora.nwra.com
> Boulder, CO 80301 http://www.cora.nwra.com
> _______________________________________________
> discuss mailing list discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20140312/45647d03/attachment.html>
More information about the discuss
mailing list