-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/13 09:27, Jeff Squyres (jsquyres) wrote:
> 2. The MPI_T performance variables are new. There's only a few
> created right now (e.g., in the Cisco usnic BTL). But the field
> is pretty wide open here -- the infrastructure is there, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/12/13 23:50, Sylvestre Ledru wrote:
> FYI, Debian has stopped supporting ia64 for its next release
> So, I stopped working on that issue.
Yeah, it's not looking good - here's the context for this:
You might want to double check that it doesn't break ABI - hypothetically,
those are equivalent (I think), but I don't know what liberties the fortran
compiler and linker is allowed to take with those different forms.
On Dec 3, 2013, at 5:37 PM, Nathan Hjelm wrote:
> For
For general use we deploy only the super stable release. We do have 1.7.x in
friendly-testing on some machines.
David, I don't think that change will break ABI so it might be worth patching
before deploying. No further 1.6.x releases are planned.
-Nathan
On Tue, Dec 03, 2013 at 10:27:43PM
On Nov 22, 2013, at 1:19 PM, Paul Kapinos wrote:
> Well, I've tried this path on actual 1.7.3 (where the code is moved some 12
> lines - beginning with 2700).
> !! - no output "skipping device"! Also when starting main processes and
> -bind-to-socket used. What I see
David --
Any possibility of upgrading to the v1.7 series?
On Nov 22, 2013, at 10:46 AM, "Barrett, Brian W" wrote:
> David (Gunter) -
>
> Which version of Open MPI are you using? It looks like the 1.7 series
> does not declare the internal version (GREEK / SVN) in the
I'm sorry; I really wasn't paying attention to my email the week of SC, and
then I was on vacation for the Thanksgiving holiday. :-\
More below.
On Nov 20, 2013, at 4:13 PM, Compres wrote:
> I was at the birds of a feather and wanted to talk to the Open MPI
> developers,
thanks
what magic "-mca base_verbose" param should print it?
On Tue, Dec 3, 2013 at 6:59 PM, Nathan Hjelm wrote:
> This usually happens when a string that belongs to the MCA system is freed
> elsewhere. Can you find out the name of the variable that is being
> destructed
> in
This usually happens when a string that belongs to the MCA system is freed
elsewhere. Can you find out the name of the variable that is being destructed
in frame 2.
-Nathan Hjelm
Application Readiness, HPC-5, LANL
On Tue, Dec 03, 2013 at 02:53:29PM +0200, Mike Dubman wrote:
>Hi,
>We
Hi,
We observe crash during shmem_finalize() (in trunk) with new MCA framework.
After investigation, found that MCA tears-down process can access
previously released memory. (reproduced with oshmem_hello_c.c test)
0 0x7fffed3d51d0 in ?? ()
#1
#2
On 20/09/2013 21:49, Sylvestre Ledru wrote:
> Hello,
>
> In Debian, we are in the process of switching the default MPI
> implementation from version 1.4 to 1.6.
>
> Every architectures are fine beside ia64. Any program based on OpenMPI
> 1.6.5 is freezing.
FYI, Debian has stopped supporting ia64
11 matches
Mail list logo