Jed,
On 2/10/2016 12:18 AM, Jed Brown wrote:
Did anyone suggest violating the standard?
if i understand correctly what George wrote earlier, then yes, removing
predefined datatypes from the header files can be seen as a violation of
the standard
in your configure script, you can simply try to
Then we should clarify the spec, because it's unreasonable to require MPI
support a Fortran type without being able to know its representation.
Jeff
On Tuesday, February 9, 2016, George Bosilca wrote:
> The text you pinpoint is clear about the target: the MPI bindings. The
> question here is no
The only agreement we have so far is that from the perspective of a user
having a questionable usage of a particular datatype in a extremely
particular reduction operation the situation can be perceived as unfriendly.
Your argument is that if in a particular OMPI installation Fortran support
is no
The text you pinpoint is clear about the target: the MPI bindings. The
question here is not about bindings, but about a predefined datatype, a
case where I don't think the text applies.
George.
On Tue, Feb 9, 2016 at 6:17 PM, Jeff Hammond wrote:
> "MPI-3.0 (and later) compliant Fortran bindi
Hello Ralph, Dave,
Thank you for your suggestions. Let me check on the nfs mounts.
The problem is I am not the grid administrator. I'm working with the grid
administrator to get it resolved. If I had my way, I would be probably
using Sun Grid.
Thank you Dave for pointing out something that I had
"MPI-3.0 (and later) compliant Fortran bindings are not only a property of
the MPI library itself, but rather a property of an MPI library together
with the Fortran compiler suite for which it is compiled." (MPI 3.1 Section
17.1.7).
Of course, implementations can provide support in excess of the m
Dave Love writes:
> Jed Brown writes:
>
>> Isn't that entirely dependent on the Fortran compiler? There is no
>> universal requirement that there be a relationship between Fortran
>> INTEGER and C int, for example.
>
> In case it's not generally obvious: the compiler _and its options_.
> You c
Gilles Gouaillardet writes:
> Jed,
>
> my 0.02US$
>
> we recently had a kind of similar discussion about MPI_DATATYPE_NULL, and
> we concluded
> ompi should do its best to implement the MPI standard, and not what some of
> us think the standard should be.
Did anyone suggest violating the standar
On Feb 9, 2016, at 12:21 AM, George Bosilca wrote:
>
> Sorry to spoil the fun here, but this proposal is a very bad idea. It is
> mandated by the MPI standard, page 25 line 27 (v3.1), not only to provide all
> predefined datatypes, but to have support for them. There are optional
> datatypes,
Rahul Pisharody writes:
> Hello all,
>
> I'm trying to get a simple program (print the hostname of the executing
> machine) compiled with openmpi run across multiple machines on Univa Grid
> Engine.
>
> This particular configuration has many of the ports blocked. My run command
> has the mca opti
Jed Brown writes:
> George Bosilca writes:
>
>> Now we can argue if DOUBLE PRECISION in Fortran is a double in C. As these
>> languages are interoperable, and there is no explicit conversion function,
>> it is safe to assume this is the case. Thus, is seems to me absolutely
>> legal to provide t
Jed,
my 0.02US$
we recently had a kind of similar discussion about MPI_DATATYPE_NULL, and
we concluded
ompi should do its best to implement the MPI standard, and not what some of
us think the standard should be.
in your configure script, you can simply try to compile a simple fortran
MPI hello w
George Bosilca writes:
> Now we can argue if DOUBLE PRECISION in Fortran is a double in C. As these
> languages are interoperable, and there is no explicit conversion function,
> it is safe to assume this is the case. Thus, is seems to me absolutely
> legal to provide the MPI-required support for
Sorry to spoil the fun here, but this proposal is a very bad idea. It is
mandated by the MPI standard, page 25 line 27 (v3.1), not only to provide
all predefined datatypes, but to have support for them. There are optional
datatypes, but MPI_DOUBLE_PRECISION (which is explicitly the base
predefined
14 matches
Mail list logo
