[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MPI-2.1 corrections, Batch 2 / AlltoallW
Jim,
so it's still in the current (?) Fortran standard. How do those vendors
like Cray get by that force REAL=DOUBLE PRECISION=64 bit, like on the T3E?
Best regards
Hans-Christian
// pallas GmbH ............ Hans-Christian Hoppe .......
Hermuelheimer Str. 10 Chief Technology Officer
D-50321 Bruehl, Germany Hans-Christian.Hoppe@pallas.com
fax +49-(0)2232-1896-29 phone +49-(0)2232-1896-0
http://www.pallas.com direct +49-(0)2232-1896-11
............................................................
James Cownie
<jcownie@etnus.c To: mpi-21@mpi-forum.org
om> cc:
Sent by: Subject: Re: MPI-2.1 corrections, Batch 2 / AlltoallW
owner-mpi-21@mpi
-forum.org
19.07.2001 15:34
Please respond
to mpi-21
Hans-Christian mentioned :-
> Of course, INTEGER (and REAL) in Fortran then would need to be 64
> bits wide also, which raises the issue about whether DOUBLE PRECISION
> is 128 bits, as would be required by Fortran 77.
And Fortran95 too :-
A scalar object of type default integer, default real, or default
logical occupies one numeric storage unit. Defaul complex and
default double precision real values occupy two consecutive numeric
storage units.
I don't see this being removed from Fortran until both COMMON and
EQUIVALENCE are also removed...
-- Jim
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com