I see a segfault show up in trunk testing starting with r26598 when
tests like
ibm collective/struct_gatherv
intel src/MPI_Type_free_[types|pending_msg]_[f|c]
are run over openib. Here is a typical stack trace:
opal_convertor_create_stack_at_begining(convertor = 0x689730,
sizes),
On Jun 14, 2012, at 3:53 PM, Ralph Castain wrote:
> I believe we use that constant in several places to define a static array
> size - you might check to be safe.
I can't find it used anywhere in the code base other than mpi.h.in.
It's a non-standard name (i.e., it's not in the MPI spec). I b
I believe we use that constant in several places to define a static array size
- you might check to be safe.
On Jun 14, 2012, at 11:52 AM, Jeff Squyres wrote:
> WHAT: Remove non-standard MPI_MAX_NAME_LEN from mpi.h.
>
> WHY: It looks like this was a carryover from LAM/MPI, but it's not in any M
WHAT: Remove non-standard MPI_MAX_NAME_LEN from mpi.h.
WHY: It looks like this was a carryover from LAM/MPI, but it's not in any MPI
spec.
WHERE: mpi.h
TIMEOUT: This seems non-controversial, so I'll set the timeout to the teleconf
next Tuesday: June 19, 2012
--
More details:
MPI_MAX_NAM
This sounds like a good thing to me. +1
On Jun 13, 2012, at 12:58 PM, Nathan Hjelm wrote:
> What: hide btl segment keys from PML/OSC code.
>
> Why: As it stands new BTLs with larger segment keys (smcuda for example)
> require changes in both OSC/rdma as well as the PMLs. This RFC makes will
>
