[MPI3 Fortran] Deprecate mpif.h?

Supalov, Alexander alexander.supalov at intel.com
Fri Mar 5 06:35:29 CST 2010

Thanks. I get your point.

-----Original Message-----
From: mpi3-fortran-bounces at lists.mpi-forum.org [mailto:mpi3-fortran-bounces at lists.mpi-forum.org] On Behalf Of N.M. Maclaren
Sent: Friday, March 05, 2010 1:01 PM
To: MPI-3 Fortran working group
Subject: Re: [MPI3 Fortran] Deprecate mpif.h?

I don't want to follow this further, but shall just try to correct
one misapprehension.

On Mar 5 2010, Supalov, Alexander wrote:
> I'm afraid you miss my point. As soon as I just say "use mpi3" in an 
> application that used "include mpif.h" or "use mpi" before, I have to 
> recheck, possibly rewrite, rebuild, revalidate, and recertify my 
> application on all OS, platforms, compilers even if I don't change 
> anything else, including the compiler. This is a huge hit that seems to 
> be ignored on this thread.
> I understand this. However, even if I change a tiny part of a mission 
> critical application, full revalidation/recertification may be necessary, 
> which takes months of calendar time and huge resources.

Fine.  But, in that case, won't you also have to revalidate and
recertify if you change to using non-blocking collectives, anyway?

I should SERIOUSLY hope that you are, as adding more asynchronicity is
one of the most common causes of introducing errors into 'working and
tested' programs.  If any 'safety critical' project does NOT require
that when changing from synchronous to asynchronous primitives, even in
minor ways, the people who specify the revalidation and recertification
requirements should be shot.

As far as I know, there is no intention to WITHDRAW the old interfaces,
so you can carry on as at present if you don't make any major changes.

But, if you want to use major new features (and non-blocking collectives
ARE a major new feature), then you will have to bite the bullet and put
of with the cost of changing to use the new module, revalidation and
recertification.  Changing the module is simple and reliable, and the
latter are forced upon you as soon as you use the new features, anyway.

Nick Maclaren.

mpi3-fortran mailing list
mpi3-fortran at lists.mpi-forum.org
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

More information about the mpiwg-fortran mailing list