On May 31, 2012, at 7:29 AM, Jeff Squyres wrote:
>>> We should have AC macros for all of these already.
>>
>> OK, I'll try find them to support (1) usecase described below.
>
> No, I'll find them -- sorry, I meant to look them up before I sent the last
> mail. Let me look them up and get back
On Thu, May 31, 2012 at 2:29 PM, Jeff Squyres wrote:
> Ah, good point. But in those cases, MPI specifically defines that those
> arguments are wholly ignored on non-root processes. So you could still even
> pass <&foo, MPI_DATATYPE_NULL>, or , and it would be ok.
I see. If this warning is im
On May 31, 2012, at 7:22 AM, Dmitri Gribenko wrote:
>> I can't think of a case offhand where it's acceptable to pass
>> MPI_DATATYPE_NULL to an MPI function. I could be missing something,
>> though... (actually, I guess I can think of some cases -- we have some
>> regression test programs tha
On Thu, May 31, 2012 at 2:07 PM, Jeff Squyres wrote:
> On May 30, 2012, at 7:04 PM, Dmitri Gribenko wrote:
>> +must_be_null specifies that the expression should be a null
>> +pointer constant, for example:
>> +
>> +
>> +
>> +/* In mpi.h */
>> +extern struct mpi_datatype mpi_datatype_null
>> + _
On May 30, 2012, at 7:04 PM, Dmitri Gribenko wrote:
> +must_be_null specifies that the expression should be a null
> +pointer constant, for example:
> +
> +
> +
> +/* In mpi.h */
> +extern struct mpi_datatype mpi_datatype_null
> +__attribute__(( type_tag_for_datatype(mpi, void, must_be_null) )
