Internal compiler error (C0000005) with latest compiler

Internal compiler error (C0000005) with latest compiler

When I compile this code in debug mode I get:

Compiling with Intel(R) Visual Fortran Compiler XE [IA-32]... ifort /debug:full /Od /Qip /extend_source:80 /d_lines /Qcoarray:shared /Qpar-report0 /Qvec-report0 /warn:all /debug-parameters:used /Qsave /align:dcommons /align:sequence /module:"Debug/" /object:"Debug/" /check:all /libs:static /threads /c /switch:coarray_opts /Qvc10 /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Intel Fortran\Microsoft Files\VC\\bin" "C:\Users\chris\Documents\Visual Studio 2010\Projects\snapclus v4.4\PS.f90" Intel(R) Visual Fortran Compiler XE for applications running on IA-32, Version Build 20130728 Copyright (C) 1985-2013 Intel Corporation. All rights reserved.

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

compilation aborted for C:\Users\chris\Documents\Visual Studio 2010\Projects\snapclus v4.4\PS.f90 (code 1)

SnapClus - 1 error(s), 0 warning(s)

It compiles OK under Release mode.

I seem to remember that internal compiler errors are an Intel problem?


Downloadapplication/octet-stream ps.f902.04 KB
6 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Thanks for the test case - we'll investigate. We are aware of a case with generics that triggers an internal compiler error, we'll see if yours is the same. Yes, Internal Compiler Error is always a compiler bug, no matter what source triggered it. If we have a workaround for this I'll let you know. Sorry for the trouble.

Retired 12/31/2016

Thanks Steve, as always. It worked fine with the previous release.

Turn off /Qip as a workaround - you wouldn't want that for a debug configuration anyway. I'll let the developers know. Issue ID is DPD200247867.

By the way, you should no longer need the ERROR STOP workaround in 14.0.

Retired 12/31/2016

Thanks Steve. Good news about ERROR STOP as well.


This problem apparently got fixed as a side-effect of something else. In any event the internal compiler error is gone in 14.0.1.

Retired 12/31/2016

Leave a Comment

Please sign in to add a comment. Not a member? Join today