catastrophic error: **Internal compiler error: internal abort**

[sknobat]

Hi 

I was trying to compile the stringifor project on windows 10/x64 platform (https://github.com/szaghi/StringiFor). I get this scary message. I attached a copy of of simplified solution (Visual Studio 2015 professional). Hope this is helpful.

Regards

Sam KV

1>stringifor_string_t.f90
1>010101_14247
1>catastrophic error: **Internal compiler error: internal abort** Please report this error along with the circumstances in which it occurred in a Software Problem Report.  Note: File and line given may not be explicit cause of this error.
1>compilation aborted for D:\Compilation\IVF_Bug\IVF_Bug\stringifor_string_t.f90 (code 1)

[Steven_L_Intel1]

Thanks, we'll check it out. An internal compiler error is always a compiler bug. Thanks for providing a complete test case. The one thing missing is the exact compiler version you used. I can see it is 16.0, but which update?

[sknobat]

Thank for your quick response

here it is (I used About menu in Visual Studio not console /? switch) 

Intel® Parallel Studio XE 2016 Update 3 Composer Edition for Fortran Windows*     Package ID: w_comp_lib_2016.3.207
Intel® Parallel Studio XE 2016 Update 3 Composer Edition for Fortran Windows* Integration for Microsoft Visual Studio* 2015, Version 16.0.0062.14, Copyright © 2002-2016 Intel Corporation. All rights reserved.
* Other names and brands may be claimed as the property of others.

[Steven_L_Intel1]

Perfect - thanks. Stay tuned....

[Steven_L_Intel1 · Accepted solution]

Sorry for dropping the ball on this.

I can reproduce the ICE only if /check:bounds is specified. It builds fine if you don't enable this- at least for stringifor_string_t.f90

I'll send this on to the developers. Issue ID is DPD200414845.

[Stefano_Zaghi]

Dear Sam and Steve,

thank you for your help.

I like to add some data. The same ICE happens on Arch Linux (a GNU Linux distro) with Intel Fortran Compiler 16.0.3 and 17.0.0 Beta only when check-bounds is invoked.

My best regards.

[Steven_L_Intel1]

That doesn't surprise me. It's rare for a compiler bug like this to be OS-dependent.

[Steven_L_Intel1]

I am told that this bug will be fixed for Update 2 to Parallel Studio XE 2017.