oopssorryit is in Intel MPI library. Thanks!!!
On Fri, Mar 13, 2009 at 9:47 PM, Ralph Castain wrote:
> Hmmm...your comments don't sound like anything relating to Open MPI. Are you
> sure you are not using some other MPI?
>
> Our mpiexec isn't a script, for example, nor do we have anythi
Hi Ben,
ben rodriguez wrote:
I have compiled ompi and another program for use on another rhel5/x86_64
machine, after transfering the binaries and setting up environment variables is
there anything else I need to do for ompi to run properly? When executing my
prog I get:
You know this all looks very similar to the reason why rolfv putback
r20351 which essentially defined out restrict within
opal_config_bottom.h when using Sun Studio.
--td
List-Post: users@lists.open-mpi.org
Date: Fri, 13 Mar 2009 16:40:49 -0400
From: Jeff Squyres
Subject: Re: [OMPI users] PGI
Yes, it does.
It re-looking at this problem, it seemed to me:
1. The real fix is to talk to the AC people and get something like
AC_CXX_RESTRICT. The PGI compiler is one place where "restrict"
support may be different in the C and C++ compilers. I'm not sure
what the Right answer is ther
Oops! I sent the patch to George but didn't send it to everyone
else. Here's a patch showing how I propose to fix this problem:
Index: ompi/mca/op/op.h
===
--- ompi/mca/op/op.h(revision 20777)
+++ ompi/mca/op/op.h(working
On Mar 13, 2009, at 5:15 PM, Mikael Djurfeldt wrote:
On Fri, Mar 13, 2009 at 9:28 PM, Jeff Squyres
wrote:
> No you should not need to do this.
>
> Is there any chance you could upgrade to Open MPI v1.3?
Yes. It works without a Barrier under v1.3. Is this a known problem?
Possibly...? I
On Mar 12, 2009, at 12:43 PM, Robert Latham wrote:
I'm using openmpi-1.3 in this example, linux, gcc-4.3.2, configured
with nothing special.
If I run the following simple C code under valgrind, single process, I
get some errors about reading and writing already-freed memory:
Hmm. This is an
Can you send all the information here:
http://www.open-mpi.org/community/help/
(including the network information)
Thanks!
On Mar 13, 2009, at 9:12 PM, Raymond Wan wrote:
Hi Jeff,
Jeff Squyres wrote:
> On Mar 13, 2009, at 6:17 AM, Raymond Wan wrote:
>
>> What doesn't work is:
>>
>> [
Sorry for the delay in replying; this week unexpectedly turned
exceptionally hectic for several us...
On Mar 9, 2009, at 2:53 PM, justin oppenheim wrote:
Yes. As I indicated earlier, I did use these options to compile my
program
MPI_CXX=/programs/openmpi/bin/mpicxx
MPI_CC=/programs/openmpi
Sorry for the late reply.
Basically, any MPI application will do. If you can run it in a
heterogeneous scenario, then it works. I don't think we have many/any
specific tests for heterogeneous scenarios that are different than our
"normal" (homogeneous) tests.
On Mar 5, 2009, at 11:30 A
George --
Any particular reason you fixed it this way?
On Mar 10, 2009, at 1:40 PM, Åke Sandgren wrote:
On Tue, 2009-03-10 at 09:23 -0800, Eugene Loh wrote:
> Åke Sandgren wrote:
>
> >Hi!
> >
> >Valgrind seems to think that there is an use of uninitialized
value in
> >mca_mpool_sm_alloc, i
Both machines are x86_64, although one is a single quad core and the other is a
dual quad core, the RH installs are the same. ompi and the other program were
both statically linked. After the compiles I copied the target dirs to the new
machine and hoped they would run, the program I wish to ru
Hi there:
I'm trying to install an old version of openmpi 1.1.1
on a 32 bit cluster and running a program with it. This program runs fine for
another 64 bit
cluster which has openmpi 1.1.1 installed, but when running this on the 32 bit
cluster, I get the
following error:
/var/spool/pbs/mom_pri
Based on my understanding of the MPI standard, the attribute copy and
delete functions have to be called every time we duplicate or free a
communicator (if the attribute is attached to it). As in this
particular case, the copy function is empty (redirected to
MPI_NULL_COPY_FN) it should be
I set it based on the only available information we have in the init
function. This way the variable is always initialized, and the upper
layer (whatever it is) has the responsibility to set it to something
useful.
Looking at the code it seems that the upper layer in question is the
mpool
Looks like I'm the first to say it: 1.1.1 is very, very old.
Are you saying that you want to install with 1.1.1 because your code is
known to work with it, or that it's known not to work with later
versions (1.3 is released)?
Either way, a later OMPI version is what you want. If your app doesn't
16 matches
Mail list logo
