Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Seg fault caused by allocate statement with source variable

lopes8070
Beginner
2,117 Views
Another compiler catastrophoc error. This time there is an allocate statement with a source definition. There are 3 classes in play. 2 classes (C,H) extend a third (D). There is a pointer (same thing happens with allocate attribute) to an object of class D defined in the main program. I then allocate the pointer with the source defined as one of either C or H (Trying to them make it of that type which is known only at runtime.

Source code attached.

Upon compilation:

echo "Compiling with F90=ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface and CC=icc"
Compiling with F90=ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface and CC=icc
make compile TARGET=demo \
F77="ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface " F90="ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface " CXX="icc" \
CC="icc" LINKER="ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface " \
FFLAGS="" CFLAGS="-O2 -g"
echo "Compiling" Program.f90
Compiling Program.f90
ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface -c Program.f90
: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.

compilation aborted for Program.f90 (code 3)
make[1]: *** [Program.o] Error 3
make: *** [ifort] Error 2
0 Kudos
22 Replies
Kevin_D_Intel
Employee
452 Views
I planned on posting about both. I want to ensure the fix is in the 11.1 branch in advance of code cutoff for update 6. That will give both of us peace of mind.
0 Kudos
Kevin_D_Intel
Employee
452 Views

My apologies. I lost track of my commitment to reply earlier. I did justconfirm the fix for (Internal tracking id: DPD200148482 - internal error with SOURCE=) is in 11.1 Update 6.

0 Kudos
Reply