Thanks Ralph,
I'll keep an eye out...
-Josh
Ralph Castain wrote:
Sometime Jan, would be my best guess...but I am not in charge of it, so don't
take that as any kind of commitment.
On Dec 28, 2009, at 5:59 PM, Joshua Bernstein wrote:
Ralph Castain wrote:
You definitely shouldn't
Sometime Jan, would be my best guess...but I am not in charge of it, so don't
take that as any kind of commitment.
On Dec 28, 2009, at 5:59 PM, Joshua Bernstein wrote:
>
>
> Ralph Castain wrote:
>> You definitely shouldn't ship that one - it may build, but it doesn't work.
>> We are looking
Ralph Castain wrote:
You definitely shouldn't ship that one - it may build, but it doesn't work. We
are looking at a bug in that code branch prior to releasing.
I have no plans to ship that one. Any idea when we'll see a 1.4.1 release?
-Josh
You definitely shouldn't ship that one - it may build, but it doesn't work. We
are looking at a bug in that code branch prior to releasing.
On Dec 28, 2009, at 3:54 PM, Joshua Bernstein wrote:
>
>
> Jeff Squyres wrote:
>> Sorry -- I neglected to update the list yesterday: I got the RM approva
Jeff Squyres wrote:
Sorry -- I neglected to update the list yesterday: I got the RM approval and
committed the fix to the v1.4 branch. So the PGI fix should be in last
night's 1.4 snapshot.
Could someone out in the wild give it a whirl and let me know if it works for
you? (it works for *me*)
Hi Ilya
Did you recompile HPL with OpenMPI, or just launched the MPICH2
executable with the OpenMPI mpiexec?
You probably know this, but you cannot mix different MPIs at
compile and run time.
Also, the HPL maximum problem size (N) depends on how much
memory/RAM you have.
If you make N too big, t
Good day, everyone!
I have problem while running HPL benchmark with OPENMPI 1.3.3.
When problem size (Ns) smaller 1 - all is good. But when I set Ns
to 17920 (for example) - I get errors:
===
[ums1:05086] ../../ompi/datatype/datatype_pack.h:37
Pointer 0xb27752c0 size 4032 is outside [
