+1
> On Jul 14, 2015, at 4:06 PM, Ralph Castain wrote:
>
> +1
>
>> On Jul 14, 2015, at 12:35 PM, Nathan Hjelm wrote:
>>
>>
>> That last sentence got mucked up somehow. Should read
>>
>> Anyone still interested in alpha support can use the gcc sync atomics or
>> sitck with 1.10 and earlier.
This one does seem like a bug. I'll open an issue.
> On Aug 14, 2015, at 3:08 PM, George Bosilca wrote:
>
> Another issue, maybe a little bit more unsettling.
>
> If I iterate over the existing pvars, and for each after retrieving their
> name I use the name to search for the associated index
On Aug 15, 2015, at 8:05 AM, Jeff Squyres (jsquyres) wrote:
>
> 2. The current implementation says that the cvar's *value* should not be
> returned, but perhaps we should be returning its *info* (even after the cvar
> is no longer available). That's a good point -- we might need to fix that.
On Aug 14, 2015, at 2:36 PM, George Bosilca wrote:
>
> For this particular test I used the current master (022a9d8).
>
> I reread the MPI_T chapter and [as usual] there might be something that
> cautions the current behavior (aka. returning MPI_T_ERR_INVALID_INDEX for an
> index smaller than t
On a Linux/x86-64 system I have configure with
--enable-debug --with-verbs --with-portals4=[path] --with-libfabric=[path]
--with-tm=[path] --disable-io-romio
Configured that way all is fine. However, if I additionally pass
--enable-static --disable-shared
the I see the following build failure:
