<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>I have a bit of experience to report. I found that if the application that I was trying to study was very sensitive to compiler and MPI versions, that I needed to build Darshan with those elements. Codes not sensitive to compiler and MPI versions, not
so sensitive to build of Darshan.</div>
<div><br>
</div>
<div>I didn’t dive down to debug the problem, just reporting my observation.</div>
<div><br>
</div>
<div>- RIchard</div>
<div>
<div><br>
</div>
<div>====================================================</div>
<div><br>
</div>
<div>Richard Hedges</div>
<div>Customer Support and Test - File Systems Project</div>
<div>Development Environment Group - Livermore Computing</div>
<div>Lawrence Livermore National Laboratory</div>
<div>7000 East Avenue, MS L-557</div>
<div>Livermore, CA 94551</div>
<div><br>
</div>
<div>v: (925) 423-2699</div>
<div>f: (925) 423-6961</div>
<div>E: richard-hedges@llnl.gov</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:darshan-users-bounces@lists.mcs.anl.gov">darshan-users-bounces@lists.mcs.anl.gov</a>> on behalf of Phil Carns <<a href="mailto:carns@mcs.anl.gov">carns@mcs.anl.gov</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, September 9, 2015 at 10:38 AM<br>
<span style="font-weight:bold">To: </span>Chih-Song Kuo <<a href="mailto:csk@ictgmbh.net">csk@ictgmbh.net</a>>, "<a href="mailto:darshan-users@lists.mcs.anl.gov">darshan-users@lists.mcs.anl.gov</a>" <<a href="mailto:darshan-users@lists.mcs.anl.gov">darshan-users@lists.mcs.anl.gov</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Darshan-users] Different builds for each MPI/compiler<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/09/2015 10:55 AM, Chih-Song Kuo wrote:<br>
</div>
<blockquote cite="mid:87a4f2c30c214f849fdb0599734c2517@LUCKMAN.anl.gov" type="cite">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;" lang="DE">Von:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;" lang="DE"><a class="moz-txt-link-abbreviated" href="mailto:darshan-users-bounces@lists.mcs.anl.gov">
darshan-users-bounces@lists.mcs.anl.gov</a> [<a class="moz-txt-link-freetext" href="mailto:darshan-users-bounces@lists.mcs.anl.gov">mailto:darshan-users-bounces@lists.mcs.anl.gov</a>]
<b>Im Auftrag von </b>Phil Carns<br>
<b>Gesendet:</b> Mittwoch, 9. September 2015 15:52<br>
<b>An:</b> <a class="moz-txt-link-abbreviated" href="mailto:darshan-users@lists.mcs.anl.gov">
darshan-users@lists.mcs.anl.gov</a><br>
<b>Betreff:</b> Re: [Darshan-users] Different builds for each MPI/compiler<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 09/09/2015 06:55 AM, Chih-Song Kuo wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:36.0pt">Hello Darshan user community,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">I just started using Darshan. Despite it runs pretty well, I wonder if I have to create different builds for each combination of MPI and compiler. I had this concern because you wrote some issues about libfmpich.so.
I as a sales consultant of an HPC-system vendor run benchmarks with many combinations of MPI and compilers to advise our customer the best choice.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Your insight will be greatly appreciated.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Chih-Song<o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
Hi Chih-Song,<br>
<br>
I have two pieces of information that might be helpful:<br>
<br>
a) The underlying compiler generally doesn't matter as much as the MPI library itself. We usually compile Darshan itself with GNU compilers for maximum compatibility; the resulting Darshan library should be compatible with most any compiler/linker.<br>
<br>
b) As for the MPI library, the MPICH ABI compatibility initiative (<a moz-do-not-send="true" href="https://www.mpich.org/abi/">https://www.mpich.org/abi/</a>) should help in theory by making sure that quite a few of the MPI implementations have a compatible
binary interface. Our team hasn't tested this capability first hand, so I can't guarantee it will work, but I think the prospects are good.<br>
<br>
thanks,<br>
-Phil<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Phil,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks. It looks like I might be worrying too much. According my experience with IPM’s I/O profiling module, different MPIs seem to have some difference in the appearance of the “const” modifier which caused
some trouble in the compilation.</span></p>
</div>
</blockquote>
<br>
This would mainly be an issue for mixing MPI 2 and MPI 3 implementations (const correctness is part of the latter spec). I imagine there would be more significant roadblocks to that level of interoperability though. It's probably best to at least stick to
one major version or the other for a given Darshan build.<br>
<br>
FWIW Darshan does detect the const issue at compile time (for the Darshan library itself), so you can build a version of Darshan for use with either API generation.<br>
<br>
<blockquote cite="mid:87a4f2c30c214f849fdb0599734c2517@LUCKMAN.anl.gov" type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Also, on <a moz-do-not-send="true" href="https://www.nersc.gov/users/software/debugging-and-profiling/ipm/">
</a><a class="moz-txt-link-freetext" href="https://www.nersc.gov/users/software/debugging-and-profiling/ipm/">https://www.nersc.gov/users/software/debugging-and-profiling/ipm/</a>, there seems to be some module explicitly built for Intel compilers. I thought
Darshan uses a similar profiling technique, so I was asking.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
</blockquote>
<br>
I don't believe this is the case. Darshan's various instrumentation methods (link-time wrappers, PMPI, or preloading) are all compiler-independent to my knowledge. IPM captures more in-depth information so it may rely on additional methods.<br>
<br>
<blockquote cite="mid:87a4f2c30c214f849fdb0599734c2517@LUCKMAN.anl.gov" type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I read in some Darshan research papers that the tool has been enabled by default on several NERSC clusters. Do the users there have a wide choice of MPI implementations? Do you have any clue which MPIs are chosen
by the user and also get successfully profiled by Darshan?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
</blockquote>
<br>
I don't have that information myself, sorry. I know that Darshan works with each of the compilers that are available (and users do switch those for various reasons), but I'm not sure about the MPI implementations.<br>
<br>
thanks,<br>
-Phil<br>
<br>
<blockquote cite="mid:87a4f2c30c214f849fdb0599734c2517@LUCKMAN.anl.gov" type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chh-Song<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
</blockquote>
<br>
</div>
</div>
</span>
</body>
</html>