There has been an internal compiler error (C0000005)

[cgerdb]

Could anyone help me? Please!

I just installed Visual Fortran 11.1.051 with Visual Studio 2008 in 64bit XP. I can build my Fortran programs in a console window using ifort command, but I cannot build anyone of them from Visual Studio. I got a lot of internal compiler errors. Here is a extremely simple example:

[plain]      program Console1

      implicit none

      CHARACTER*10 FNAME
      DATA FNAME /'ABCDEFG'/
      INTEGER I, J

       DO J=1,LEN(FNAME)
!         IF (J.NE.3) THEN
         IF (FNAME(J:J).NE.' ') THEN
           I=I+1
         ENDIF
       ENDDO

     
      end program Console1

[/plain]

The compiler accept the commented IF line, but not the uncommented IF line!

[ArturGuzik]

Quoting - cgerdb

Could anyone help me? Please!

I just installed Visual Fortran 11.1.051 with Visual Studio 2008 in 64bit XP. I can build my Fortran programs in a console window using ifort command, but I cannot build anyone of them from Visual Studio. I got a lot of internal compiler errors. Here is a extremely simple example:

[plain]      program Console1

      implicit none

      CHARACTER*10 FNAME
      DATA FNAME /'ABCDEFG'/
      INTEGER I, J

       DO J=1,LEN(FNAME)
!         IF (J.NE.3) THEN
         IF (FNAME(J:J).NE.' ') THEN
           I=I+1
         ENDIF
       ENDDO

     
      end program Console1

[/plain]

The compiler accept the commented IF line, but not the uncommented IF line!

Hi,

you might have some VS integration problems. I just tried this on x64 VS2008 Pro on W7 and it builds OK. Did installation go fine?

A.

[Steven_L_Intel1]

Please attach the buildlog.htm from the Debug or Release folder.

[cgerdb]

Quoting - Steve Lionel (Intel)

Please attach the buildlog.htm from the Debug or Release folder.

Thank you, Steve. The buildlog is attached. It has mixed English and Japanese messages.

[cgerdb]

Quoting - ArturGuzik

Hi,

you might have some VS integration problems. I just tried this on x64 VS2008 Pro on W7 and it builds OK. Did installation go fine?

A.

The installation went very well. I tried uninstall and install many times with different packages. The result is the same.

[Steven_L_Intel1]

Would you please ZIP your project folder and attach it here? I can't reproduce it so far.

If you open a Fortran Build Environment command prompt window and try to compile from that, with "ifort console1.f90", does it compile? Start > Programs > Intel Software Development Tools > Intel Visual Fortran Compiler 11.1.051 > Fortran Build Environment for Applications running on IA-32

[cgerdb]

Quoting - Steve Lionel (Intel)

Would you please ZIP your project folder and attach it here? I can't reproduce it so far.

If you open a Fortran Build Environment command prompt window and try to compile from that, with "ifort console1.f90", does it compile? Start > Programs > Intel Software Development Tools > Intel Visual Fortran Compiler 11.1.051 > Fortran Build Environment for Applications running on IA-32

The zipped project folder has been attached. Thanks.

[cgerdb]

Quoting - Steve Lionel (Intel)

Would you please ZIP your project folder and attach it here? I can't reproduce it so far.

If you open a Fortran Build Environment command prompt window and try to compile from that, with "ifort console1.f90", does it compile? Start > Programs > Intel Software Development Tools > Intel Visual Fortran Compiler 11.1.051 > Fortran Build Environment for Applications running on IA-32

Sorry, I forgot to answer your second question in my previous message.

Yes, I can compile console1.f90 using ifort.

[cgerdb]

Hi! Steve,

Inspired by your suggestion that solves my problem with fftpack5, I did some experiments and solved this problem as well.

What I did is copy the command line options in the fortran project property window and use them with ifort command. I delete options one by one to see which causes the problem. It turns out that /check:bounds is evil. After I set the "Run-time/Chech Array and String Bounds" to "no", I successfully build console1.f90 and my other programs.

Thanks a lot.

[Steven_L_Intel1]

Yes, that's exactly the technique I use when diagnosing a problem like this. However, your code compiled fine for me with bounds checking. Thanks for the project - I'll try that next.

[Les_Neilson]

A minor point - not sure if it is related to the actual problem, butin the code shownvariable I is not initialised

Les

[Hitoshi]

Quoting - Steve Lionel (Intel)

Yes, that's exactly the technique I use when diagnosing a problem like this. However, your code compiled fine for me with bounds checking. Thanks for the project - I'll try that next.

This problem seems similar tomy case reported here on Nov. 13, which is specific to IVF Japanese edition 11.1.051 andoccurs only under the debug mode.
The workaround I found for this is choosing one of the followings;
1) add compiler option "/Qdiag-message-catalog-"
or
2) get rid of "/check:bounds" diagnostics during debugging mode
The former is preferable, because "check:bounds" is always meaningful at the debugging stage.

BTW, Japanese users who use Windows Japanese edition are forced to install automatically Japanese mode IVF, which sometimes becomes troublemaker.
Personally, I want to use original IVF English version to share the technical terms and to avoid such troubles like above mentioned, unfortunately this kind of issues is not the first time.
But you can not use original IVF version if your OS locale is Japanese.
I will be very happy if we Japanese users can select the original IVF version during installation.

[Steven_L_Intel1]

Yes, it is exactly the problem Hitoshi describes, and this will be fixed in Update 4, due out early next week. The suggestion to use /Qdiag-message-catalog- is the recommended workaround, though disabling bounds checking works too.