topic Re: Internal compiler error in Intel® Fortran Compiler

Internal compiler error

f2003 — Wed, 27 Jun 2007 05:25:55 GMT

hi,all:

fortcom aborted and reported an error message when compiling:
0_11517
fortcom:Severe:**Internalcompilererror:internalabort**PleasereportthiserroralongwiththecircumstancesinwhichitoccurredinaSoftwareProblemReport.Note:Fileandlinegivenmaynotbeexplicitcauseofthiserror.
compilationabortedfortest.f90(code3)

can anybody give me an advice?
BTW,this program passed when compiled by g95 and gfortran.

thanks.

==================================
moduleout
implicitnone
real,dimension(20)::a_ref,l_ref,x_ref,y_ref,z_ref
character(len=30)surname(20)
real,dimension(20,6)::fxyz
integer,dimension(:,:),allocatable::ncross
real,dimension(:,:),allocatable::xcro
commona_ref,l_ref,x_ref,y_ref,z_ref,fxyz,surname

endmoduleout

moduleblk3
implicitnone
integer,dimension(:),allocatable::nxt,nyt,nzt
integer::il,jl,kl,i2,j2,k2,nm
commonil,jl,kl,i2,j2,k2,nm
endmoduleblk3

moduleblk5
implicitnone
real,dimension(:,:,:,:),allocatable::x,y,z
endmoduleblk5

moduleblk6
implicitnone
integer::nobl,a
commonnobl,a
endmoduleblk6

modulebc
implicitnone
integer::r
commonr
integer,dimension(:),allocatable::bc_type,bc_xyz,bc_dir,&
bc_block,bc_iblock,bc_norm
integer,dimension(:,:),allocatable::bc_surf,bc_order,bc_uvw,&
bc_start,bc_end,&
&nb sp;bc_istart,bc_iend
endmodulebc

moduleblk7
implicitnone
real::nobl2
!commonnobl2
endmoduleblk7

programmain

useout

useblk3
useblk5
useblk6
usebc
useblk7

implicitnone

real::aref,lref,xref,yref,zref
character(len=10)type
integer::block,iblock,nxyz
integer,dimension(20)::surf
integer,dimension(3)::start,end,istart,iend,order
real,dimension(5)::uvw

namelist/surface/aref,lref,xref,yref,zref
namelist/bcin/type,block,start,end,iblock,istart,iend,&
surf,order,nxyz,uvw
!

open(11,file='gri3d.dat',status='old')

open(17,file='euler.bc')

read(11,*)nobl

allocate(nxt(nobl))
allocate(nyt(nobl))
allocate(nzt(nobl))

end

Re: Internal compiler error

Steven_L_Intel1 — Wed, 27 Jun 2007 14:36:39 GMT

The standard advice for all compilers - report the problem to the vendor. (In this case, use Intel Premier Support.)

Re: Internal compiler error

Steven_L_Intel1 — Wed, 27 Jun 2007 15:08:55 GMT

I took a quick look - the compiler doesn't like the fact that nobl and nobl2 are both module variables and in COMMON. This is legal, but something is confusing the compiler. A workaround is to not have either of these variables in COMMON - you may not need them to be.

Please do report this to Intel Premier Support. When you do, reference T78388.

Re: Internal compiler error

f2003 — Fri, 29 Jun 2007 06:58:04 GMT

thank you.

Re: Internal compiler error

Steven_L_Intel1 — Fri, 29 Jun 2007 13:22:19 GMT

Are you aware that variables nobl and r are effectively EQUIVALENCEd? Why do you have these in COMMON? It's unusual to put COMMONs in modules - the only reason to do so is if your application also contains sources originally written to use COMMON and not modules.

Re: Internal compiler error

f2003 — Sun, 01 Jul 2007 02:11:55 GMT

yes it is a ill program but it abides by the rules of fortran.

Re: Internal compiler error

Steven_L_Intel1 — Mon, 02 Jul 2007 13:58:58 GMT

I agree it is legal and that there is a compiler bug. But I thought you might not be aware of the effects of putting those variables in COMMON.

A workaround is to use named COMMON and not blank COMMON.

Re: Internal compiler error

f2003 — Wed, 04 Jul 2007 01:40:37 GMT

you are right.

thanks again.