<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I want to draw your attention to a pull request (<a href="https://urldefense.us/v3/__https://github.com/pmodels/mpich/pull/6950__;!!G_uCfscf7eWS!Z0Q_JoqFA2r7SkLiJkQr76fZRC6M-dSJ3MFTJfItvBu5o415oABIbOjB0WdXyfMuwFmlE60iIiY$" id="LPlnk">https://github.com/pmodels/mpich/pull/6950</a>) to remove the
<code>--enable-error-messages</code> configure option. By default, MPICH maintains and will print an error stack on error abort, something like the following:</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<pre><div style="font-size: 12pt; color: rgb(0, 0, 0);"><code>atal error in MPI_Init: Other MPI error, error stack:
MPIR_Init_thread(377): Initialization failed
MPID_Init(90)........: channel initialization failed
MPID_Init(357).......: PMI_Init returned -1</code></div></pre>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The other error message levels do not maintain such error stacks and will only print generic messages without instance details or simply no error messages. To my knowledge, no users are annoyed by the detailed error stack messages. Thus PR6950 removes the
options altogether to simplify the code maintenance. After the PR, we'll always maintain the detailed error message stack. There are still CVAR variables `MPIR_CVAR_PRINT_ERROR_STACK` and `MPIR_CVAR_CHOP_ERROR_STACK` to control the verbosity of the error messages,
as well as `MPIR_CVAR_ERROR_CHECKING` to enable/disable error checking.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I don't expect there will be an impact on users, but if you are using the <code>--enable-error-messages</code> configure option, please let us know.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
--</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hui Zhou</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
</body>
</html>