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

got an internal compiler error (C0000005) in IVF 2017

An_N_1
New Contributor I
447 Views

My old project making trouble again!

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

After update to VS2107 and IVF2017(update4, w_comp_lib_2017.4.210), there is an internal compiler error. I have tried to make the question more clear by cutting try the codes. Finally I could repeat the error by some brief code and compiler option. But I don't know if it is a general case, after all people around won't update the compiler as often as I..

My simple code as below. And the error only occur in debug configure by set 'Debug information format' to Full (/debug:full), and 'Inforamtion for parameter constant' to All (/debug-parameters:all).

There is no problem with IVF2015 and some early versions I have in hand.

module M


implicit none


character(LEN=40), public, parameter :: Name = "Name"
  
contains
   
subroutine foo1 ()
implicit none
    call foo2(Name)
end SUBROUTINE

end module

 

0 Kudos
1 Solution
Lorri_M_Intel
Employee
447 Views

Unfortunately, when the original problem was fixed, it was fixed only for numeric data.   The character parameter fix will be available in a future update.

                     --Lorri

View solution in original post

0 Kudos
5 Replies
mecej4
Honored Contributor III
447 Views

A workaround to consider in such situations is to fall back to an older version of the compiler (on your machine or another) for compiling just the one file (or just those files) that triggered an ICE with the current compiler. In other words, do manual intervention to supply the OBJ file that the newer compiler is unable to produce.

0 Kudos
An_N_1
New Contributor I
447 Views

Thanks!

BTW: My compiler version is update4(w_comp_lib_2017.4.210). But the defect seems not be fixed..

0 Kudos
Lorri_M_Intel
Employee
448 Views

Unfortunately, when the original problem was fixed, it was fixed only for numeric data.   The character parameter fix will be available in a future update.

                     --Lorri

0 Kudos
An_N_1
New Contributor I
447 Views

Thanks for all!

0 Kudos
Reply