<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We should look at this again. Many years ago, autoconf supported a local cache, but it didn't do it correctly - it would use the cache even when the cache values did not correspond to the environment. A common error was to use the cache even when configuring with a different compiler or compiler flags, thus picking up incorrect results. After several wasted days tracking down problems that were due to autoconf's broken cache system, we (that means I) added aclocal_cache.m4 to our local autoconf macros; this redefines AC_CACHE_LOAD. There are also routines to save and load the cache for subsidiary configure invocations.<div><br></div><div>But that was a long, long time ago. Today's autoconf is vastly different and may be more robust in how it handles caching.<br><div><div><br></div><div>Bill</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="font-size: 12px; ">William Gropp</div><div style="font-size: 12px; ">Director, Parallel Computing Institute</div></div></div></span><span class="Apple-style-span" style="font-size: 12px; ">Thomas M. Siebel Chair in Computer Science</span><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="font-size: 12px; ">University of Illinois Urbana-Champaign</div></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On May 21, 2014, at 8:26 PM, Rob Latham wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><br>On 05/21/2014 03:35 PM, Yida Wang wrote:<br><blockquote type="cite">I have to use icc since I want to run code on Intel Xeon Phi. Also, I<br></blockquote><blockquote type="cite">tried to install MPICH2 since it claims to support Intel-MIC<br></blockquote><blockquote type="cite">architecture and is open source.<br></blockquote><br>long ago, autoconf used to support a local cache. sadly, that appears not to work, despite the continued presence of a --cache-file command line parameter. It was perfect for just these kinds of situations: for but one example, mpich looks for stdint.h twice.<br><br>==rob<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">BTW, still configuring. It's faster to do it locally (both the source<br></blockquote><blockquote type="cite">code and the Intel compiler), but encountered a Fortran type length<br></blockquote><blockquote type="cite">detection error (don't remember the exact error information now, it<br></blockquote><blockquote type="cite">recommended me to "Consider setting CROSS_F77_SIZEOF_INTEGER to the<br></blockquote><blockquote type="cite">length in bytes of a Fortran INTEGER") last run.<br></blockquote><br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite">YW<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Wed, May 21, 2014 at 4:28 PM, Jed Brown <<a href="mailto:jed@jedbrown.org">jed@jedbrown.org</a><br></blockquote><blockquote type="cite"><<a href="mailto:jed@jedbrown.org">mailto:jed@jedbrown.org</a>>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Kenneth Raffenetti <<a href="mailto:raffenet@mcs.anl.gov">raffenet@mcs.anl.gov</a><br></blockquote><blockquote type="cite"> <<a href="mailto:raffenet@mcs.anl.gov">mailto:raffenet@mcs.anl.gov</a>>> writes:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> > The Intel compilers could also be a source of slowdown. Are they<br></blockquote><blockquote type="cite"> > installed on a network filesystem? They may also call out to a<br></blockquote><blockquote type="cite"> network<br></blockquote><blockquote type="cite"> > license server each time they are invoked for a compile test.<br></blockquote><blockquote type="cite"> Does just<br></blockquote><blockquote type="cite"> > compiling a small program take a long time with icc, ifort, etc.?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> The system headers and libraries are also often on a network file<br></blockquote><blockquote type="cite"> system. Although moving the source tree to a local disk usually<br></blockquote><blockquote type="cite"> provides some improvement, I rarely find it getting anywhere close to<br></blockquote><blockquote type="cite"> the performance of a cheap laptop because most of the file accesses<br></blockquote><blockquote type="cite"> performed by the compiler are hitting the network anyway. This is the<br></blockquote><blockquote type="cite"> price we all pay for legacy file system semantics and dumb compiler<br></blockquote><blockquote type="cite"> architecture. I think most companies in a place to change these things<br></blockquote><blockquote type="cite"> do full local installs on their development boxes so that compilation is<br></blockquote><blockquote type="cite"> fast. And the HPC vendors wear blindfolds and put their heads in the<br></blockquote><blockquote type="cite"> sand.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> As for Intel license servers, this is the price you pay for anti-piracy<br></blockquote><blockquote type="cite"> measures. People that are really ticked off by this crack their<br></blockquote><blockquote type="cite"> compilers---the pirates enjoy a better user experience. Is it ethical<br></blockquote><blockquote type="cite"> to use a cracked version if you've already paid for the licensed<br></blockquote><blockquote type="cite"> version?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Besides those issues, the Intel compiler usually takes a lot longer to<br></blockquote><blockquote type="cite"> compile. It's worth building with gcc and clang to compare. You might<br></blockquote><blockquote type="cite"> be pleasantly surprised to find that in addition to compiling faster,<br></blockquote><blockquote type="cite"> your code also runs faster (this is the case for several applications I<br></blockquote><blockquote type="cite"> work with).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> _______________________________________________<br></blockquote><blockquote type="cite"> discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a> <<a href="mailto:discuss@mpich.org">mailto:discuss@mpich.org</a>><br></blockquote><blockquote type="cite"> To manage subscription options or unsubscribe:<br></blockquote><blockquote type="cite"> <a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br></blockquote><blockquote type="cite">To manage subscription options or unsubscribe:<br></blockquote><blockquote type="cite"><a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote><blockquote type="cite"><br></blockquote><br>-- <br>Rob Latham<br>Mathematics and Computer Science Division<br>Argonne National Lab, IL USA<br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a><br></div></blockquote></div><br></div></div></div></body></html>