An "Internal compiler error" indicates a bug in Intel Fortran (a segfault
in this case), and not in anything the compiler is trying to build- if the
code you're building has an error, the compiler should properly print out
an error statement.
You should forward this along to Intel.
> -----Original Message-----
> From: users-bounces_at_[hidden] [mailto:users-bounces_at_[hidden]] On
> Behalf Of Sangamesh B
> Sent: Wednesday, October 28, 2009 12:40
> To: OpenMPI ML
> Subject: [OMPI users] With IMPI works fine,With OMPI fails
> Hi all,
> The compilation of a fortran application - CPMD-3.13.2 - with
> OpenMP + OpenMPI-1.3.3 + ifort-10.1 + MKL-10.0 is failing with
> following error on a Rocks-5.1 Linux cluster:
> /lib/cpp -P -C -traditional -D__Linux -D__PGI -DFFT_DEFAULT -DPOINTER8
> -DLINUX_IFC -DPARALLEL -DMYRINET ./potfor.F ./potfor.f
> /opt/mpi/openmpi/1.3.3/intel/bin/mpif90 -c -pc64 -O3 -xT -unroll -
> ./potfor.f -o ./potfor.o
> fortcom: Severe: **Internal compiler error: segmentation violation
> raised** Please report this error along with the circumstances in which
> occurred in a Software Problem Report. Note: File and line given may
> be explicit cause of this error.
> compilation aborted for ./potfor.f (code 3)
> make: *** [potfor.o] Error 3
> But if the potfor.f is compiled by removing -openmp option, then it
> successfully. But while running it again failed with "Aborted"
> The interesting thing is, the same application compiles and runs fine
> with IntelMPI on another cluster with exactly the same environment.
> What's here the issue with Open MPI?