Intel® Fortran Compiler for Linux* and Mac OS X*

List Directed I/O Error

Hi,

As can be seen in the attached program, when I am trying to open, read and write data into an array, I am getting an error which says as follows:

"forrtl: severe (59): list-directed I/O syntax error".

Any suggestions or insight into this would be greatly helpful.

Thank you.

swapping in windows 10

Although Visual Studio and other applications appeared to remain in working order after the (very time consuming) Windows Update installation of windows10 tech preview, none of my Intel software tools except Impi came up by themselves.  The culprit appeared to be multiple visible versions even though the latest had been installed with the choice to replace the previous. Impi also had 2 visible versions, but that didn't stop it from coming up. Un-installing everything possible and re-installing seemed to recover, but then I had to find  a working ifort.cfg elsewhere.

Memory not released after DEALLOCATE

 I am working as a software developer in a company with a code based on FORTRAN 90. Recently we have found that code was failing with lack of enough memory at some stage of the run. Tests have shown that using the "Deallocate" makes the pointers used "unassociated", but for some pointers the memory is not released. This could be a large amount causing the code to crash eventually. The situation becomes worse as we are allocating and deallocating the same pointers several times during the runtime.

error #6405: The same named entity from different modules and/or program units cannot be referenced.

Hi,

I am getting the error message from the title when compiling the code in which there are many modules having the initialisation procedures with the same name, init. Normally, when the various modules use each other, I mask those init procedures with use somemodule, forgetme => init. However, intel fortran compiler 13.1.3 20130607 fails to compile it and, what is worse, it is not easy to say where exactly the error originates from, since it is issued from some temporary .i90 file the compiler made as it went about its business.

We now have the reverse problem with the Intel 15.0.1 compiler on RHEL6 x86_64: building a shared...

We now have the reverse problem with the Intel 15.0.1 compiler on RHEL6 x86_64: building a shared object with -shared but without -static-intel still results in the inclusion of libifcore_pic.a in the corresponding shared object. This is a problem because when later an OpenMP-enabled Fortran program wants to use the library, the incompatible run-times cause the binary to segfault at launch.

Is this already known? Should I prepare a test case?

 

Subscribe to Intel® Fortran Compiler for Linux* and Mac OS X*