Internal compiler error in Composer XE

[chstoyer]

While trying to build a project being ported from CVF, I encountered an internal compiler error:

1>PLOT_RHO.f90

1>fortcom: Fatal: There has been an internal compiler error (C0000005).

1>compilation aborted for C:\\IX1Dv2\\PLOT_RHO.f90 (code 1)

1>

1>Build log written to "file://C:\\IX1Dv2\\Debug\\BuildLog.htm"

BuilLog and source attached. Thanks for any help.

I am also having problems with behavior of a subroutine being correct when in debug mode and incorrect when in release mode. Again, this is a port from CVF. I will try to dig up a small sample and send later.

Charles

[chstoyer]

I forgot to attach the modules that are used by the source code. Here they are.

[Steven_L_Intel1]

Thanks, we'll take a look at this.

[chstoyer]

It looks as if this is going to take a long time. Any suggestions to figuring out what line of code is causing it so maybe I can modify the code to avoid the error and get on with this?

I have found two issues with the compiler so far. I would have thought version 12 would be mature!

Charles

[Steven_L_Intel1]

Sorry for the delay.

I'm missing WINTERACTER.MOD - if I comment out the USE of that module, it compiles. Do you have the source to that file? I think Winteracter provides it. What if you add the .f90 to your project and compile it?

We had this version in beta test for six months at hundreds of users, but my experience over the decades is that no amount of testing finds all problems.

Also, what happens if you turn off "Check Routine Interfaces" under Diagnostics?

[mecej4]

Are you using a release of Winteracter (i.e.,modules and libraries) that is suitable for use with Intel Fortran?

If you are trying to use the Winteracter files from a Winteracter for CVF release, the attempt will most likely fail.

[Steven_L_Intel1]

True, but the failure in that case ought not to be an ICE.

[chstoyer]

Well, I am moving to a new machine (Win 7 home pro) and can't really move until everything is working. So I am not in a big hurry, but I have a year free maintenance on the new compiler and would like to get it going. Not being my main machine, I sometimes don't look at it for a while as I wait.

I added winteracter.f90 to my project and the internal compiler error is still there. I am getting caught at a lot of nitpicking items that the CVF overlooked, so I guess my codes will become more robust with the new version.

I am attaching Winteracter.MOD and it's source.

I realize no amount of testing finds all problems, but I am having two. Haven't bothered you too much with the second one yet.

If I turn off "Check Routine Interfaces", it compiles but does not link due to unresolved externals. I am having some problems there I will need to address and get back to you. Let me know if you find the problem so I can turn the routine interface checking back on. I do have a similarproject that compiles and links so I am sure I can figure that one out.

One additional complaint/question, is that in Word (Office 2000, 2003 and 2010) and in the 2000 version of Visual Studio, if one selects some text and drags it with the mouse, it moves it. However if you use the RIGHT mouse button to drag it, you get choices, including move and copy. I use that a lot and it seems t be missing in VS 2010. Any idea how to turn that on?

Thanks,

Charles

[Steven_L_Intel1]

Ok, now we're getting somewhere. The problem is related to the generated interface checking. I would need a ZIP of your whole project to try to reproduce that. Turning off generated interface checking should not create link errors that were not there otherwise, so you should address those.

If you are willing, please ZIP the project sources and attach the ZIP to a reply here. If you prefer, you can use Intel Premier Support to submit the issue.

I don't know the answer to your VS2010 question. I can see what you are asking about but we don't control that aspect of VS.