[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)

To: mpi-21@xxxxxxxxxxxxx
Subject: Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
From: Greg Lindahl <lindahl@xxxxxxx>
Date: Thu, 6 Dec 2007 15:45:43 -0800
Delivered-to: mpifrm-mpi-21-outgoing@mailbouncer.mcs.anl.gov
Delivered-to: mpifrm-mpi-21@mailbouncer.mcs.anl.gov
In-reply-to: <20071206205047.GA9127@mhdmobile.lan>
References: <mp64xtryhGbQ.rSj4xqNx@smtp.gmail.com> <5ECAB1304A8B5B4CB3F9D6C01E4E21A2D3B655@swsmsx413.ger.corp.intel.com> <20071205191905.GA25173@bx9.net> <20071206103043.GC10990@mhdmobile.lan> <20071206195711.GA30147@bx9.net> <20071206205047.GA9127@mhdmobile.lan>
Reply-to: mpi-21@xxxxxxxxxxxxx
Sender: owner-mpi-21@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Thu, Dec 06, 2007 at 09:50:47PM +0100, Dries Kimpe wrote:

> You asked for more details about applications encountering problems moving
> to other MPI implementations; well, this is one example.

Thanks, I stand corrected. I was hoping someone would contact some ISVs and
find some that weren't already known.

-- greg

References:
- Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
  - From: William Yu
- RE: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
  - From: Supalov, Alexander
- Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
  - From: Greg Lindahl
- Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
  - From: Dries Kimpe
- Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
  - From: Greg Lindahl
- Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
  - From: Dries Kimpe

Prev by Date: Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
Next by Date: [mpi-21] Missing MPI::CONVERSION_FN_NULL
Previous by thread: Re: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
Next by thread: RE: [mpi-21] ABI (was: Call for MPI 2.2 and 3.0...)
Index(es):
- Date
- Thread