[MPI3 Fortran] [Fwd: Was ASYNCHRONOUS..., New: ACCESSES ( ) suffix

[Aleksandar Donev]

On Wednesday 10 September 2008 11:26, Bill Long wrote:
>  The message to the compiler (in this example) is that a
> Call to MPI_Wait may access the actual argument corresponding to the
> buffer dummy argument in any call to either MPI_ISend or MPI_IRecv that
> is visible.  This would explicitly suppress the undesired code motion.
Answer this simple question:
Why is this not needed/done for the Fortran WAIT statement?
Why is MPI_Wait soo different and why does it require this super hideous hacks 
to make it work?
Why is a simple barrier to code motion (like WAIT or SYNC MEMORY) sufficient?
Best,
Aleks

-- 
Aleksandar Donev, Ph.D.
Lawrence Postdoctoral Fellow @ Lawrence Livermore National Laboratory
High Performance Computational Materials Science and Chemistry
E-mail: donev1 at llnl.gov
Phone: (925) 424-6816  Fax: (925) 423-0785
Address: P.O.Box 808, L-367, Livermore, CA 94551-9900
Web: http://cherrypit.princeton.edu/donev