Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29234 토론

Any hope for CVF internal compiler error?

lklawrie1
초급자
732 조회수
We've started getting an internal compiler error with CVF 6.6C.
It appears to be related to inline initialization of a derived type. (i.e., we take that out and it goes away).
It's error C5
Might this have a known work around? I'm sure it's not going to be fixed.
Linda
0 포인트
6 응답
Steven_L_Intel1
732 조회수
That is an access violation error. You can try writing to vf-support@compaq.com and see if you get a response.

Steve
0 포인트
Intel_C_Intel
직원
732 조회수
Linda,
Are you sure of the cause? And is it repeatable? Weoccasionally get 'internal compiler errors' that are solved by restarting Visual Studio or adding / removing a blank line or two from the problem source file.
Admittedly, they aren't so prevalent with CVF 6.6C as they were with previous versions, but I've still seen them.
Dan

Message Edited by Judd on 03-14-2005 10:29 AM

0 포인트
lklawrie1
초급자
732 조회수
Thanks, Steve and Dan.
I sent a message to vf-support -- got the usual standard reply.
we know how to get the compiler to accept it -- just take off the inits for one derived type. or even one developer said it only crashes after assigning the 5th (or maybe the 6th) in that type.
So, it's not a show stopper -- just an annoyance.
Linda
0 포인트
Steven_L_Intel1
732 조회수
How does it work in Intel Fortran? I know you have that.
0 포인트
lklawrie1
초급자
732 조회수
No problem in Intel Fortran. I'm using that for my major parts of development but many of the others are still with CVF.
Linda
0 포인트
lklawrie1
초급자
732 조회수
Hey, hey. Not only did they reply to me, I actually got a query this morning for a small build that duplicated the problem.
Even better, as I was trying to make it, I figured out the problem!
In short, one of the "data only" modules had included a public module that should only be used in several of our modules, not propagated throughout the entire code. That "seems" to have been causing the problem.
Mostly, our routine modules (modules that contain routines) are "private" except for one or two public routines.... But we have a couple where, for limited use, the entire module and routines are exposed publicly.
Linda
0 포인트
응답