FYI, you might want to try falling back on the previously mentioned
2017.2.174.
If you do update to a newer version, the 2019 update 3 (and perhaps 2018
versions) have a serious memory leak issue:
https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/msg18404.html
Intel implemented a fix for that in the 2019 update 4 that you might
want to try. However, it seems that the fix hasn't been confirmed if it
working as mentioned in the Intel forum here:
https://software.intel.com/en-us/comment/1930019
Also, if you use 2019 update 4 and have any issues with mpirun (or
mpiexec.hydra), you might need to configure it to use the old legacy
version of it, refer to:
https://software.intel.com/en-us/forums/intel-clusters-and-hpc-technology/topic/812229
On 7/3/2019 2:02 AM, Luc Fruchter wrote:
Indeed, I am using ifort 208.3.222 with the options:
-O2 -FR -mp1 -w -prec_div -pc80 -pad -ip -DINTEL_VML -traceback
-assume buffered_io -I$(MKLROOT)/include
I will try to change the options / update ifort to a newer version.
_______________________________________________
Wien mailing list
Wien@zeus.theochem.tuwien.ac.at
http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
SEARCH the MAILING-LIST at:
http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html
