Intel Software Network - feed

ICE with 11.1.059

Tue, 24 Nov 2009 13:35:54 -0800

Just came across this ICE, which happened both with 11.1.059 and 11.1.046. Not sure what I did that triggered it... I was in the process of changing a bunch of dummy arguments from automatic to allocatable deferred arrays. The full command was:

ifort -I. -Isrc/ -Isrc2/ -fpp -warn all -fpp -check all -gen-interfaces -assume realloc_lhs -static -pg -warn notruncated_source -debug full -traceback -O0 -g -FR -c -o lmain.o /gusr/alr99/cluster/workspace/frealix/src/lmain.f90

Not sure what info might be needed... I attach the lmain.f90 file (sorry, it's pretty ugly in there!)

shared libraries with Intel runtime libs

Tue, 24 Nov 2009 11:27:31 -0800

When compiling sources and linking via Intel compilers with -static-intel (the default), then Intel RTE libs like libirc, libsvml, libimf are linked statically into the executable. When generating a shared library with Intel compilers, then the generated lib seems to depend on the Intel RTE shared libs, as can be seen with ldd. When linking with this library via Intel compilers, the generated a.out also seems to depend on shared RTE libs (ldd says this, and the runtime loader claims about missing libs when LD_LIBRARY_PATH is not corrent, or when the dynamic section of the shared lib does not contain the correct rpath).
My question is: Which Intel RTE libs are used at runtime of an executable, which was linked with a shared lib as given above? Does the shared lib code take some shared RTE lib loaded at runtime, while the exe code takes the static RTE code linked at link time, or is the dependency of a.out on shared RTE libs only apparent?

Template Libraries

Tue, 24 Nov 2009 07:14:22 -0800

I am getting undefined references to calls like UWRITE1, UROTATE and such. I am told these are part of some old template libraries, and the ones they are being pointed to are libt3dg.a, libtpdf.a and libtunx.a. Is there source or converted versions of these libraries for linux?

Puzzling "forrtl: severe (174)"

Mon, 23 Nov 2009 22:13:07 -0800

Ifort version 10.1
Compile flags core2 -i4 -r8 -stand f03 -vec-report0 -mcmodel=medium -shared-intel -heap-arrays 1 -warn none -g -traceback -fno-inline-functions -check all -warn declarations -warn unused

I’m working with a big, Fortran, mpi program. It works great when compiled with 11.1, but dies when compiled with 10.1. It needs to be run with both, so I’m looking for a work-around or compiler options.

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
myprograma.x.stat 0000000000E12924 Unknown Unknown Unknown

After much debugging, have narrowed it down to the below line. Note: this line executes just fine for some test cases even with 10.1.

read(File%UNIT, POS=FilePos) TBlock

TBlock(:,:) is complex(8), allocatable, and has just been allocated to a not-too-large size (less than 100x100).
FilePos is integer(8), passed in as intent(In)
File%Unit is integer
File is passed in as intent(InOut)

Any help greatly appreciated.

Laura

Strange issue with this forum

Mon, 23 Nov 2009 08:05:53 -0800

I was subscribed to one of the other forums on this site briefly while I was following some topics. I'm done, and so unsubscribed. It has successfully stopped sending me notifications regarding that forum, but I'm still getting new topic notifications for this forum, even though I never sub'd to it (and if I go to forum tools, it says I'm not subscribed). Can an admin help me out on this? Thank you!

No environment variables have been set by ifortvars.sh, MPICH can't find compiler

Mon, 23 Nov 2009 05:13:38 -0800

Installing FC for Linux finished successfully.

Using ./ifortvars.sh in my bash does work (no error message), but NO environment variables have been set.
Therefore command ifort does not work.

I set PATH, LD_LIBRARY_PATH, .bashrc and the symblic link /usr/bin/ifort by hand now.
For installing MPICH: FC=ifort and F90=ifort

But MPICH can't find the Compiler.

Which environment variables are missing ?

What's the theory of compliing VASP?

Sun, 22 Nov 2009 02:21:00 -0800

I got VASP successfully one month ago occasionally ,but I don't know the theory of compliing VASP. I major in Condensed Matter Physics who don't know Linux before research.So I want konw how can I compile VASP successfully without no errors. My notebook is Lenovo , Intel Core T5800, 120G Hard Disk, 2.0G RAM, VASP4.6 Serial Edition with Ifort 8.0 and mkl8.0. Our group has the VASP License. Thank you!

problem to install mac

Sat, 21 Nov 2009 05:08:23 -0800

how to install mac on intel?

if there is any update to install please tell me

strange valgrind info with ifort

Fri, 20 Nov 2009 06:39:04 -0800

Hi,

I'm using valgrind to analyze a code compiled with ifort, and I have some extrain information on different points of the code.
Some examples:

==2785== by 0x403CDB: main (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== Address 0x5a64178 is 112 bytes inside a block of size 116 alloc'd
==2785== at 0x4C265AE: malloc (vg_replace_malloc.c:207)
==2785== by 0x2110962: for__get_vm (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x2135456: for__open_proc (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x20F627E: for_open (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x6FCE94: c_input_mp_openfi_ (c_input.F90:798)
==2785== by 0x1DEACB2: startp_ (startp.f90:21)
==2785== by 0x13079E0: MAIN__ (mainpg.F90:82)
==2785== by 0x403CDB: main (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)

or

==2785== Invalid read of size 8
==2785== at 0x20E474F: for__io_return (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x2106DDC: for_read_seq_fmt (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x720171: c_input_mp_randwr_ (c_input.F90:1302)
==2785== by 0x720011: c_input_mp_genfil_ (c_input.F90:1283)
==2785== by 0x6FD2BA: c_input_mp_openfi_ (c_input.F90:800)
==2785== by 0x1DEACB2: startp_ (startp.f90:21)
==2785== by 0x13079E0: MAIN__ (mainpg.F90:82)
==2785== by 0x403CDB: main (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)

or

==2785== Conditional jump or move depends on uninitialised value(s)
==2785== at 0x218CE96: __intel_sse2_strlen (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x20E476B: for__io_return (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x2106DDC: for_read_seq_fmt (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)
==2785== by 0x720171: c_input_mp_randwr_ (c_input.F90:1302)
==2785== by 0x720011: c_input_mp_genfil_ (c_input.F90:1283)
==2785== by 0x6FD2BA: c_input_mp_openfi_ (c_input.F90:800)
==2785== by 0x1DEACB2: startp_ (startp.f90:21)
==2785== by 0x13079E0: MAIN__ (mainpg.F90:82)
==2785== by 0x403CDB: main (in /home/xxxx/bin/e600INTEL-dbg_2009.11.unix.exe)

I have many comments in the valgrind analysis, and I'm not sure about if is right or not....

I'm using intel ifort 11.1.056, and ubuntu 9.04 amd64:
Linux xxxx 2.6.27-15-generic #1 SMP Tue Oct 20 06:50:36 UTC 2009 x86_64 GNU/Linux

compilation: ifort -g -warn all -check all -traceback ....

Someone can give me some information about this kind of "remarks/errors" with valgrind?

Thanks.

Strange issue with Intel 10.1 fortran Compiler

Fri, 20 Nov 2009 03:04:00 -0800

Hi to everyone,

I am facing a very strange issue with the Intel fortran compiler 10.1 :
I have created a source code using CVF (Compaq Visual Fortran) on a Windows XP pc. After some modifications I have found that a subroutine in the source code was unecessary, so I removed it. I also removed the common blocks for the main program and the deleted subroutine. The source code comiles with CVF giving no warnings and no errors and the executable runs as it should. (The executable is estimated by the CVF to consume ~ 640MB of RAM)

Now I want to compile and run that source code on a Red Hat linux machine. So I compile the same source code using the intel fortran compiler 10.1, installed on the linux machine. Again no warnings and no errors. But when I try to run it, the program hangs and also, from what I can see through the top command, it consumes unexplainably high CPU and all the available memory (plus swap). The linux machine is a 2 x Quad Core Xeon and has 8GB of RAM.

The unmodified version/initial of the code worked perfectly at both machines. After changing step by step the code I have found that :
- if I just delete the subroutine and retain the common block in the main program, the executable runs.
- the problem occurs after deleting the common block of the shared variables (between the main program and the deleted subroutine) in the main program, even if there is no other subroutine using/sharing these variables.
After more tests, I have found that this happens after removing a specific variable from the block. Again I repeat that this variable is not used by any other subroutines and is defined in the main program before any calculations.

I can't understand :

- Why the program hangs on the intel compiler since I explicitly define the specific variable in the main program?

- Also why the executable from the intel fortran hangs, whereas the executable from CVF works as it should?

No special flags, optimizations etc. were used in both the CVF and Intel Fortran.

Could this be a compiler bug? Or am I missing something?

Any ideas would be appreciated.

Thanks in advance.