<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 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]--></head><body lang=EN-CA link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Dear all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have noticed a bug with the combination of lapwso_mpi (WIEN2k 17.1) and ifort 18.0.0 (20170811).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On a well-formed case that works properly when lapwso_mpi is compiled with ifort 15.0.6, I get crashes on each process shortly after startup like the following:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>forrtl: severe (24): end-of-file during read, unit 9, file /path/case/./case.vector_1<o:p></o:p></p><p class=MsoNormal>Image PC Routine Line Source<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 00000000004916D8 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 00000000004B6065 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 000000000048ABB6 get_nloat_ 16 get_nloat.f<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 000000000044A361 MAIN__ 144 lapwso.F<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 0000000000406C5E Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libc-2.12.so 0000003FA401ED5D __libc_start_main Unknown Unknown<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 0000000000406B69 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>in get_nloat.f this line is simply “read(9)”, so I’m guessing there has been some change in raw file access in this ifort version. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This crash does not seem to be dependent on optimizations, as I can reproduce it with <o:p></o:p></p><p class=MsoNormal>FPOPT=-O0 -g -FR -traceback -I$(MKLROOT)/include<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Adding –assume bufferedio (or –assume nobufferedio) does not make a difference.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Trapping the IO error on this line and exiting simply causes a later segfault, so there is something more complicated happening here than just reading off the end of the file at the end of the routine:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>forrtl: severe (174): SIGSEGV, segmentation fault occurred<o:p></o:p></p><p class=MsoNormal>Image PC Routine Line Source<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 000000000047358D Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libpthread-2.12.s 0000003BE880F7E0 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF045B23D Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF045B040 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF045AF6E Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF045C039 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF045D7CB Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF0454F6E Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libiomp5.so 00002AAEF0455B6C Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 000000000049F07B Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 000000000040C4CC rotmat_mp_init_ro 229 modules.F<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 000000000043027E MAIN__ 146 lapwso.F<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 0000000000406D5E Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal>libc-2.12.so 0000003BE7C1ED5D __libc_start_main Unknown Unknown<o:p></o:p></p><p class=MsoNormal>lapwso_mpi 0000000000406C69 Unknown Unknown Unknown<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any ideas? I may be forced to upgrade soon (some Intel cluster license SNAFU)…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='mso-fareast-language:EN-CA'>--<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-CA'>Eamon McDermott<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-CA'>CEA Grenoble<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-CA'>DRT/LETI/DTSI/SCMC<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>