[mpich-discuss] MPI_Get on the same memory location

[Balaji, Pavan]

Sorry, I was wrong, there’s no runtime option to disable this.  There’s only a runtime option to disable a similar check for collective operations.

  — Pavan

On Aug 22, 2014, at 5:18 PM, Alessandro Fanfarillo <fanfarillo at ing.uniroma2.it> wrote:

> Could you tell me which flag disables the check? I would suggest this
> procedure as temporary workaround.
> 
> Thanks
> 
> On Fri, Aug 22, 2014 at 2:41 PM, Balaji, Pavan <balaji at anl.gov> wrote:
>> 
>> On Aug 22, 2014, at 1:43 PM, Brian Van Straalen <bvstraalen at lbl.gov> wrote:
>>> Is there a significant cost to have the MPI implementation provide a check for aliasing?
>> 
>> We do check for this error by default in MPICH (which is why this email thread started).
>> 
>> There’s a way to turn off the checking through a configure flag as well as an environment variable, if needed.  But that’s essentially saying — I know it’s wrong, but I’m too lazy to fix my application.
>> 
>>  — Pavan
>> 
>> --
>> Pavan Balaji  ✉️
>> http://www.mcs.anl.gov/~balaji
>> 
>> _______________________________________________
>> discuss mailing list     discuss at mpich.org
>> To manage subscription options or unsubscribe:
>> https://lists.mpich.org/mailman/listinfo/discuss
> 
> 
> 
> -- 
> 
> Alessandro Fanfarillo
> Dip. di Ingegneria Civile ed Ingegneria Informatica
> Università di Roma "Tor Vergata"
> NCAR Office: +1 (303) 497-2442
> Tel: +39-06-7259 7719
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss

--
Pavan Balaji  ✉️
http://www.mcs.anl.gov/~balaji