[mpich-devel] MPICH_ASYNC_PROGRESS

[Balaji, Pavan]

It's still allowed.  It's autogenerated, which is why you can't find it with git grep.

Note that the supported option is MPIR_CVAR_ASYNC_PROGRESS.  MPICH_ASYNC_PROGRESS is an alias that is maintained for backward compatibility reasons.  In the future, that option might disappear.

  -- Pavan

> On Feb 11, 2016, at 12:53 AM, Jeff Hammond <jeff.science at gmail.com> wrote:
> 
> README.envvar says you still support it but it appears nowhere in the source code.  Are you parsing it via some special magic or are the docs out of sync with the implementation?
> 
> I ask this now because I saw what appears to be a bug in the implementation, but it's stupid to track down that bug if the problem is that MPICH_ASYNC_PROGRESS is not supposed to work anymore.
> 
> Thanks,
> 
> Jeff
> 
> jrhammon-mac01:git jrhammon$ git grep ASYNC_PROGRESS
> src/mpi/init/init.c:    - name        : MPIR_CVAR_ASYNC_PROGRESS
> src/mpi/init/init.c:    if (MPIR_CVAR_ASYNC_PROGRESS)
> src/mpi/init/init.c:    if (MPIR_CVAR_ASYNC_PROGRESS) {
> src/mpi/init/initthread.c:    if (MPIR_CVAR_ASYNC_PROGRESS)
> src/mpi/init/initthread.c:    if (MPIR_CVAR_ASYNC_PROGRESS) {
> (pamid stuff)
> 
> --
> Jeff Hammond
> jeff.science at gmail.com
> http://jeffhammond.github.io/
> _______________________________________________
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/devel