On Wed, 4 Jun 2008, Paul H. Hargrove wrote:
Brian states
This will allow users to turn ptmalloc2 support on/off at application
link time instead of MPI compile time.
Where I assume "MPI compile time" means when the MPI *implementation* is
compiled.
Correct.
So what about LD_PRELOAD?
On 22:33 Wed 04 Jun , Mukesh K Srivastava wrote:
> I am aware that GCC(v-4.2.4) supports OpenMP, so suggested if OMPI could be
> supported too with GCC releases?
Are you 100% sure about what an MPI implementation is?
> There is no confusion please.
There is confusion thank you very much
Sounds good to me. Thanks Brian!
On Jun 3, 2008, at 12:04 PM, Brian W. Barrett wrote:
Hi all -
Sorry this is so late, but it took a couple of iterations with a
couple of
people to get right from a technology standpoint. All mistakes in
this
proposal are my fault.
What: Fix the
On Wed, Jun 04, 2008 at 12:53:25PM +0530, Mukesh K Srivastava wrote:
>Hi OMPI Community.
>
>
>Is there any thought process to extend GCC support to OpenMPI or
>implementation of OpenMPI specification in GCC for C, C++ & Fortran and
>making it generally available for platforms which supports POSIX.
Hi OMPI Community.
Is there any thought process to extend GCC support to OpenMPI or
implementation of OpenMPI specification in GCC for C, C++ & Fortran and
making it generally available for platforms which supports POSIX.
Can GCC community think extending a support library for OpenMPI in it's
Last conf. call Jeff mentioned that he see some collectives failures.
In my MTT testing I also see that Pallas collectives failed -
http://www.open-mpi.org/mtt/index.php?do_redir=682
Alltoall
#
# Benchmarking Alltoall
#
Hello Ralph,
* Ralph Castain wrote on Tue, Jun 03, 2008 at 11:59:07PM CEST:
> Very interesting. Don't know if it's the same problem, but I noted an issue
> quite a while ago where make -jN all/install would fail when traversing
> opal. I built a workaround that was just a script that does make
