misc: Convert old wiki links to new location

CHANGES

@@ -223,7 +223,7 @@
    transport functions.
 
  # Improvements to derived datatype testing (DTPools -
-   https://wiki.mpich.org/mpich/index.php/DTPools).
+   https://github.com/pmodels/mpich/blob/main/doc/wiki/design/DTPools.md).
 
  # Added new "non-catastrophic" error codes to expose internal
    resource exhaustion.
@@ -379,7 +379,7 @@
  # Blue Gene/Q implementation supports MPI-3. This release contains a
    functional and compliant Blue Gene/Q implementation of the MPI-3 standard.
    Instructions to build on Blue Gene/Q are on the mpich.org wiki:
-   http://wiki.mpich.org/mpich/index.php/BGQ
+   https://github.com/pmodels/mpich/blob/main/doc/wiki/source_code/BGQ.md
 
  # Fortran 2008 bindings (experimental). Build with --enable-fortran=all. Must have
    a Fortran 2008 + TS 29113 capable compiler.
@@ -462,7 +462,7 @@
 
  # Several improvements to the Hydra process binding code.  See the
    Hydra wiki page for more information:
-   http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager
+   https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md
 
  # MPICH now supports operations on very large datatypes (those that describe
    more than 32 bits of data).  This work also allows MPICH to fully support

CONTRIBUTING

@@ -4,7 +4,7 @@ How to contribute to MPICH
 agreement. http://www.mpich.org/documentation/contributor-docs/
 
 2. Format your patches according to the MPICH coding
-standards. https://wiki.mpich.org/mpich/index.php/Coding_Standards
+standards. https://github.com/pmodels/mpich/blob/main/doc/wiki/source_code/Coding_Standards.md
 
 3. Use the git pre-commit hook included with MPICH
 (mpich_root/maint/hooks/pre-commit)
@@ -23,4 +23,4 @@ can be merged.
 
 More info on contributing to MPICH, including tips on how to use git,
 can be found here:
-https://wiki.mpich.org/mpich/index.php/Contributing_to_MPICH
+https://github.com/pmodels/mpich/blob/main/doc/wiki/source_code/Contributing_to_MPICH.md

README.vin

@@ -38,7 +38,7 @@ information on bug fixes and new releases.
 Note: this guide assumes you are building MPICH from one of the MPICH
 release tarballs. If you are starting from a git checkout, you will need
 a few additional steps. Please refer to the wiki page --
-https://wiki.mpich.org. 
+https://github.com/pmodels/mpich/blob/main/doc/wiki/Index.md.
 
 The following instructions take you through a sequence of steps to get
 the default configuration (ch3 device, nemesis channel (with TCP and
@@ -51,7 +51,7 @@ shared memory), Hydra process management) of MPICH up and running.
     - REQUIRED: Perl
 
     - REQUIRED: A C compiler (C99 support is required. See
-      https://wiki.mpich.org/mpich/index.php/Shifting_toward_C99)
+      https://github.com/pmodels/mpich/blob/main/doc/wiki/source_code/Shifting_Toward_C99.md)
 
     - OPTIONAL: A C++ compiler, if C++ applications are to be used
       (g++, etc.). If you do not require support for C++ applications,
@@ -228,7 +228,7 @@ shared memory), Hydra process management) of MPICH up and running.
     nothing is specified, ':1' is assumed.
 
     More details on interacting with Hydra can be found at
-    http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager
+    https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md
 
 If you have completed all of the above steps, you have successfully
 installed MPICH and run an MPI example.
@@ -246,8 +246,8 @@ environments as well as our partner institutes. If you have problems
 with the installation or usage of MPICH, please follow these steps:
 
 1. First see the Frequently Asked Questions (FAQ) page at
-http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions to
+https://github.com/pmodels/mpich/blob/main/doc/wiki/faq/Frequently_Asked_Questions.md
-see if the problem you are facing has a simple solution. Many common
+to see if the problem you are facing has a simple solution. Many common
 problems and their solutions are listed here.
 
 2. If you cannot find an answer on the FAQ page, look through previous
@@ -564,7 +564,7 @@ hydra
 Hydra is the default process management framework that uses existing
 daemons on nodes (e.g., ssh, pbs, slurm, sge) to start MPI
 processes. More information on Hydra can be found at
-http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager
+https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md
 
 gforker
 -------
@@ -738,7 +738,7 @@ where <N> is the checkpoint number you want to restart from.
 
 These instructions can also be found on the MPICH wiki:
 
-  http://wiki.mpich.org/mpich/index.php/Checkpointing
+  https://github.com/pmodels/mpich/blob/main/doc/wiki/design/Checkpointing.md
 
 -------------------------------------------------------------------------
 
@@ -748,7 +748,7 @@ For MPICH developers who want to directly work on the primary version
 control system, there are a few additional steps involved (people
 using the release tarballs do not have to follow these steps). Details
 about these steps can be found here:
-http://wiki.mpich.org/mpich/index.php/Getting_And_Building_MPICH
+https://github.com/pmodels/mpich/blob/main/doc/wiki/source_code/Github.md
 
 -------------------------------------------------------------------------
 

doc/mpich/tuning_parameters.md

@@ -13,7 +13,7 @@ runtime decisions at a finer granularity.
 Notice that performance of the application depends on how ranks are mapped to
 the cores of the processor. For information on how to specify process-core
 binding with mpirun, information is provided here:
-https://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager#Process-core_Binding.
+https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md#process-core-binding.
 
 This following section of this document provides information about threading
 optimizations (Section 1).

doc/userguide/user.tex.vin

@@ -265,7 +265,7 @@ depict the number of processes you want to run on each node. If
 nothing is specified, ':1' is assumed.
 
 More details on interacting with Hydra can be found at
-\url{http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager}
+\url{https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md}
 
 
 \subsection{Extensions for All Process Management Environments}
@@ -282,7 +282,7 @@ For the time being we will document these separately.
 MPICH provides a number of process management systems. Hydra is the
 default process manager in MPICH. More details on Hydra and its
 extensions to mpiexec can be found at
-\url{http://wiki.mpich.org/mpich/index.php/Using\_the\_Hydra\_Process\_Manager}
+\url{https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md}
 
 
 \subsection{Extensions for the gforker Process Management Environment}
@@ -493,7 +493,7 @@ Hydra process manager.  Currently only the BLCR checkpointing library
 is supported.  BLCR needs to be installed separately.  Below we
 describe how to enable the feature in MPICH and how to use it.  This
 information can also be found on the MPICH Wiki:
-\url{http://wiki.mpich.org/mpich/index.php/Checkpointing}
+\url{https://github.com/pmodels/mpich/blob/main/doc/wiki/design/Checkpointing.md}
 
 \subsection{Configuring for checkpointing}
 \label{sec:conf-checkp}
@@ -601,7 +601,7 @@ To test a pre-installed MPI implementation:
 \section{Frequently Asked Questions}
 
 The frequently asked questions are maintained online
-here:\url{http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions}
+here:\url{https://github.com/pmodels/mpich/blob/main/doc/wiki/faq/Frequently_Asked_Questions.md}
 
 \bibliographystyle{plain}
 \bibliography{user}

doc/wiki/design/New_RMA_Design.md

@@ -152,7 +152,7 @@ When a new element is needed, we first check if one is available in the
 corresponding **local** pool. If the **local** pool is empty, we try to
 find one in the **global** pool. If even the **global** pool is empty,
 we will call the **CLEANUP_WIN_AGGRESSIVE** function (see [Basic
-routines](https://wiki.mpich.org/mpich/index.php/New_RMA_Design#Basic_routines))
+routines](https://github.com/pmodels/mpich/blob/main/doc/wiki/design/New_RMA_Design.md#basic-routines))
 to free up existing elements. When we are done using an element, we
 first return it to the **local** pool. If the **local** pool is full, we
 return it to the **global** pool.
@@ -296,7 +296,7 @@ packets we are expecting from a particular target if the user calls a
 Note that there is a request pointer on window called **fence_req**
 which stores request of IBARRIER. For details on the memory barrier
 semantics, see [RMA + shared
-memory](https://wiki.mpich.org/mpich/index.php/New_RMA_Design#RMA_.2B_shared_memory).
+memory](https://github.com/pmodels/mpich/blob/main/doc/wiki/design/New_RMA_Design.md#rma--shared-memory).
 
 ```
 FENCE() {

src/mpl/include/mpl_dbg.h

@@ -12,7 +12,7 @@
 /*
  * Multilevel debugging and tracing macros.
  * The design is discussed at
- * http://wiki.mpich.org/mpich/index.php/Debug_Event_Logging
+ * https://github.com/pmodels/mpich/blob/main/doc/wiki/design/Debug_Event_Logging.md
  *
  * Basically, this provide a way to place debugging messages into
  * groups (called *classes*), with levels of detail, and arbitrary

src/pm/hydra/README

@@ -5,4 +5,4 @@ ssh, rsh, fork), as well as natively integrate with resource
 management systems (such as slurm, pbs, sge).
 
 More information about using Hydra can be found here:
-http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager
+https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md

src/pm/hydra/mpiexec/options.c

@@ -115,7 +115,8 @@ static void help_help_fn(void)
 
     printf("\n");
     printf("Please see the instructions provided at\n");
-    printf("http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager\n");
+    printf
+        ("https://github.com/pmodels/mpich/blob/main/doc/wiki/how_to/Using_the_Hydra_Process_Manager.md\n");
     printf("for further details\n\n");
 }
 

test/mpi/README

@@ -217,7 +217,7 @@ generated, he/she can use the "DTP_RUNTIME_TYPES" environment variable to limit
 number of basic types tested by the "runtest" script. If the user further wishes
 to reduce the length of the tests, he/she can also use the "DTP_MAX_OBJ_ID" environment
 variable to limit the number of datatypes tested from each pool (please refer to
-the DTPools README and wiki for more information: https://wiki.mpich.org/mpich/index.php/DTPools).
+the DTPools README and wiki for more information: https://github.com/pmodels/mpich/blob/main/doc/wiki/design/DTPools.md).
 
 DTPools also allows the user to define his/her own struct type pools. For this case
 the configuration file to be used to create the executables is "structtypetest.txt".