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

ifort 9.1, g++ mpich SIGSEGV. ifort 9.0 works

I have a program that when compiled with ifort v9.0 and g++ v3.4.5 and uses mpich 1.2.7 runs fine, but when I upgraded to ifort v9.1.039 Build 20060927Z, crashes with:

p1_23035: p4_error: interrupt SIGSEGV: 11
rm_l_1_23052: (0.791327) net_send: could not write to fd=5, errno = 32
p1_23035: (0.803600) net_send: could not write to fd=5, errno = 32

It is a mixed combination of FORTRAN compiled with ifort, and C code compiled with g++, and linked with g++. I have the FORTRAN modules in mpich compiled with v9.1.

core 2 duo and ifort em64t problem


I am trying to use the em64t compiler in a core 2 duo processor, but I have some problems. I don't know if I need some special configuration, but I have error in the compilation process.

ifort -c test test.f90

/opt/intel/fce/9.1.039/bin/fortcom: error while loading shared libraries: wrong ELF class: ELFCLASS64
compilation aborted for test.f90 (code 127)

Its a problem with the 64bit version of the libraries??


Can I catch Fortran RTL errors in C?

I am calling a fortran function from C++ code in a try/catch block. For certain inputs, I get the following RTL error:

forrtl: severe (64): input conversion error, unit -5, file Internal Formatted Read

I would like to catch this error, and any others, in the C code and print a message like "the Fortran function had an error" to a file.

My code is :

retval = CHARMM(); // The fortran function
switch (retval) {
case 0: fprintf(stderr, "SUCCESS - Charmm exited with code %i.
", retval);

IOSTAT behavior in ifort?

Hi guys,

I can't seem to understand why iostat is behaving the way it does when it compiles. Here is the program:


INTEGER :: x,k


read (*,*, iostat=k ) x

write (*,*) k, 'this is the iostat value'
if ( k == 0 ) exit

write (*,*) 'Now out of loop'


Help on some run-time error with ifort compiler for Linux.


I have meet a very strange problem.
One of my program can run with a
small array, but if the array is become bigger, there will be an
run-time error, the error meeage like this:

*** glibc detected *** double free or corruption (!prev): 0x0824b550

forrtl: error (76): IOT trap signal

I had checked the the boundary of the array, it's ok.

I am wander what's meaning about the error message, is it means that
the glibc is not right in my PC ?

Thanks a lot for everyone to read it.:)

How to download IFORT using FTP under SSH?

I am trying to download the Fortran Compiler for Linux using FTP. I am
using a secure conection (SSH) to one of our remote Linux machines and
from there I would like to download the zip/tar file. The procedure
should be also the same from Windows.

In your web page the FTP address of the file is:

Hence, I try:

Floating Point Calculation output changes from ifort 9.0 to 9.1.039

I am compiling using

ifort -O3 -save -r8 -mp -fp-port -std95 -CB -traceback -fpstkchk

This is a very complex calculation and I cannot include the code (over 50 files). When I change between ifort 9.0.021 to 9.1.039, I get differences in the 7th or 8th significant digit. I either need to know what change would have caused this, or a flag to enable to get the original output.


forrtl: error (78): process killed (SIGTERM)


I get the following runtime error on our Beowulf cluster with an parallel MPI Code compiled with ifort:

forrtl: error (78): process killed (SIGTERM)
PSIlogger: Child with rank 0 exited with status 1.

PSIlogger: done

How can I find out more about this error, where and why it
occurs? Debugging works not for the parallel code for some reason.

Thanks in advance,


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