There is already a nice solution for the useful special case of ABI
portability where one wants to use more than one MPI library with an
application binary, but only one MPI library for a given application
invocation:
https://github.com/cea-hpc/wi4mpi
They document support for the Intel MPI and O
Don't forget that there's a lot more to "binary portability" between MPI
implementations than just the ABI (wire protocols, run-time interfaces,
...etc.). This is the main (set of) reasons that ABI standardization of the
MPI specification never really took off -- so much would need to be
stand
On 09/20/17 23:39, Jeff Hammond wrote:
I assume that anyone who is using Fortran 2003 or later has the good sense to
never use compiler flags to change the size of the INTEGER type, because this
is evil.
Actually, only changing INTEGER size without adjusting REAL size is evil (i.e.
breaks assu
This discussion started getting into an interesting question: ABI
standardization for portability by language. It makes sense to have ABI
standardization for portability of objects across environments. At the same
time it does mean that everyone follows the exact same recipe for low level
implement
On Wed, Sep 20, 2017 at 5:55 AM, Dave Love
wrote:
> Jeff Hammond writes:
>
> > Please separate C and C++ here. C has a standard ABI. C++ doesn't.
> >
> > Jeff
>
> [For some value of "standard".] I've said the same about C++, but the
> current GCC manual says its C++ ABI is "industry standard",
On Wed, Sep 20, 2017 at 6:26 AM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:
> On Tue, Sep 19, 2017 at 11:58 AM, Jeff Hammond
> wrote:
>
> > Fortran is a legit problem, although if somebody builds a standalone
> Fortran
> > 2015 implementation of the MPI interface, it would be dec
On Tue, Sep 19, 2017 at 11:58 AM, Jeff Hammond wrote:
> Fortran is a legit problem, although if somebody builds a standalone Fortran
> 2015 implementation of the MPI interface, it would be decoupled from the MPI
> library compilation.
Is this even doable without making any assumptions ?
For exam
Jeff Hammond writes:
> Intel compilers support GOMP runtime interoperability, although I don't
> believe it is the default. You can use the Intel/LLVM OpenMP runtime with
> GCC such that all three OpenMP compilers work together.
For what it's worth, it's trivial to make a shim with a compatible
Jeff Hammond writes:
> Please separate C and C++ here. C has a standard ABI. C++ doesn't.
>
> Jeff
[For some value of "standard".] I've said the same about C++, but the
current GCC manual says its C++ ABI is "industry standard", and at least
Intel document compatibility with recent GCC on GNU/
; >>
>> >>
>> >>
>> >>
>> >> Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone
>> >>
>> >> Original message
>> >> From: Michael Thomadakis
>> >> Date: 9/18/17 3:51 PM
t;
> >>
> >>
> >> Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone
> >>
> >> ---- Original message ----
> >> From: Michael Thomadakis
> >> Date: 9/18/17 3:51 PM (GMT-05:00)
> >> To: users@lists.open-mp
d be possible. This is not so for Fortran libraries
> or
> >> Windows.
> >>
> >>
> >>
> >>
> >>
> >>
> >> Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone
> >>
> >> ---- Origina
gt;> g++ that this should be possible. This is not so for Fortran libraries
> or
> >> Windows.
> >>
> >>
> >>
> >>
> >>
> >>
> >> Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone
> >>
>
M (GMT-05:00)
>> To: users@lists.open-mpi.org
>> Subject: [OMPI users] Question concerning compatibility of languages used
>> with building OpenMPI and languages OpenMPI uses to build MPI binaries.
>>
>> Dear OpenMPI list,
>>
>> As far as I know, w
Question concerning
compatibility of languages used with building OpenMPI and languages OpenMPI
uses to build MPI binaries.
Dear OpenMPI list,
As far as I know, when we build OpenMPI itself with GNU or Intel compilers we
expect that the subsequent MPI application binary will use the same compiler
set
; Windows.
>
>
>
>
>
>
> Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone
>
> Original message
> From: Michael Thomadakis
> Date: 9/18/17 3:51 PM (GMT-05:00)
> To: users@lists.open-mpi.org
> Subject: [OMPI users] Question concerning com
riginal message
> From: Michael Thomadakis
> Date: 9/18/17 3:51 PM (GMT-05:00)
> To: users@lists.open-mpi.org
> Subject: [OMPI users] Question concerning compatibility of languages used
> with building OpenMPI and languages OpenMPI uses to build MPI binaries.
>
> Dear Op
Date: 9/18/17 3:51 PM (GMT-05:00) To:
users@lists.open-mpi.org Subject: [OMPI users] Question concerning
compatibility of languages used with building OpenMPI and languages OpenMPI
uses to build MPI binaries.
Dear OpenMPI list,
As far as I know, when we build OpenMPI itself with GNU or I
Dear OpenMPI list,
As far as I know, when we build OpenMPI itself with GNU or Intel compilers
we expect that the subsequent MPI application binary will use the same
compiler set and run-times.
Would it be possible to build OpenMPI with the GNU tool chain but then
subsequently instruct the OpenMPI
19 matches
Mail list logo
