"Jeff Squyres (jsquyres)" <jsquy...@cisco.com> writes: > As I mentioned Craig and I debated long and hard to change that > default, but, in summary, we apparently missed this clause on p610. > I'll change it back.
Okay, thanks. > I'll be happy when gfortran 4.9 is released that supports ignore TKR > and you'll get proper interfaces. :-) Better for everyone. >> I don't call MPI from Fortran, but someone on a Fortran project that I >> watch mentioned that the compiler would complain about such and such a >> use (actually relating to types for MPI_Status in MPI_Recv rather than >> buffer types). > > Can you provide more details here? Choice buffer issues aside, I'm > failing to think of a scenario where you should get a compile mismatch > for the MPI status dummy argument in MPI_Recv... Totally superficial, just passing "status(1)" instead of "status" or "status(1:MPI_STATUS_SIZE)". I extrapolated: how can they provide an explicit interface to MPI_Recv in "use mpi", given portability constraints/existing language standards?
pgpCIfMJ5CYnP.pgp
Description: PGP signature
