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

ifort 9.0 error on emt64/amd_x86_64 mode

Hi folks,

I have recently attempted to port my code to the ifort compiler
running on amd opteron processors, but have run up against a link
time error that I don't understand. The code compiles fine
on both xeon machines and itanium machines, with the compiler
installations there.

The error that I get (multiple times for different variables) is as follows:

tree.F: relocation truncated to fit: R_386_32 against symbol `treevars_mp_natom_' defined in COMMON section in treevars.o

Fortran 9.0 on SUSE Linux later than 9.1

Iwant toinstall Intel Fortran 9.0 on SUSE Linux. According to the intel system requirements, SUSE 9.1 has been verified to work. What about SUSE 9.2 and 10.0, do they work together with FORTRAN?
Or is RedHat a better choice?
I use an Opteron K8SE Motherbord with 2 DUal-core cpus.
Best regards
Anders Salwn

-fast compiler option

when i use the -fast option to compile and then attempt to run the resulting program i get the message

Fatal Error : This program was not built to run on the processor in your system

do I have to set something somewhere so that the compiler knows what processor type to use or should it do it by itself. I'm using a sonoma machine... might this be a problem?

Thanks for any help you can give

Segmentation faul, dinamicallly allocated matrix

Hi, I'm using ifort 9.0 to compile a fortran 90 program that I'm developing. The problem is that I compiled it with th -g option, and when I run the program it crashes with a segmentation fault error.

I tried to track down the bug with idb, and it seems that the problem is when a subroutine uses a dinamically allocated matrix, and it can't pass the right dimensions.

Different results between CVF and IF for Linux

My code compiled with CVF runs very well under Windows XP, giving correct results. When I try to run the code making use of Intel Fortran for Linux 9.0 (under Fedora Core 4) the code gives completely different results: a very beautiful colection of zeros.

I compiled using -C option to catch any unitialized variable and the code runs well, but gives wrong results. From my experience I know that the results under XP with CVF are the correct ones.

Someone has any idea about what is going wrong?

idb debugger


A very simple question:
How do I get the debugger to stop at the line where the error occurred.

Example program is:
program tmp
integer arr(5)
do i = 1,10
arr(i) = i
print *,arr(i)
In the debugger it should stop at line 4 and tell me that the array is out of bounds.

ifort -g -debug extended -debug-parameters all tmp.f90

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