<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Let me add that Intel 2017 changed for the n-th time the way to link mkl scalapack!!! I will try commit a small change to m4 files and be backward compatible.</div><div>D.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Inviato da Tablet Samsung.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Messaggio originale --------</div><div>Da: Filippo SPIGA <filippo.spiga@quantum-espresso.org> </div><div>Data: 22/11/16 20:47 (GMT+01:00) </div><div>A: General discussion list for Quantum ESPRESSO developers <q-e-developers@qe-forge.org> </div><div>Oggetto: Re: [Q-e-developers] 'mpif.h' vs. 'include mpi' and regression tests </div><div><br></div></div>On Nov 22, 2016, at 2:05 PM, Paolo Giannozzi <paolo.giannozzi@uniud.it> wrote:<br>> Maybe we should revert to the good habit of confining MPI definitions to a very small number of files. Once upon a time there was just one in "parallel_include.f90", maybe a couple more here and there. Now:<br>> $ grep mpif.h espresso/*/*.f90 espresso/*/*/*f90 | wc -l<br>> 62<br><br>This would be a good habit but it has some issues:<br>- if mpi.mod is not comoiled with the same compiler version, it may fail at linker stage (e.g. you upgrade GCC from 4.8 to 4.9 but you do not recompile Open MPI: in case of "mpi.h" is most likely continue to work, in case of "use mpi" will most likely not)<br>- some old MPI library may miss "mpi.mod" because it has not been compiled or simply too old<br><br>So if we want to make the switch we need to ensure backward compatibility to old/legacy environments. Ideally the configure needs be able to detect if "mpi.mod" is present and use it, keeping "mpi.h" as fallback.<br><br>--<br>Filippo SPIGA ~ Quantum ESPRESSO Foundation ~ http://www.quantum-espresso.org<br><br><br>_______________________________________________<br>Q-e-developers mailing list<br>Q-e-developers@qe-forge.org<br>http://qe-forge.org/mailman/listinfo/q-e-developers<br></body></html>