Having moved from fixed arrays that were equivalenced to dynamic arrays I'd like to reinstate an equivalent to the old equivalence.
Is the run-time behavior shown below with the following code correct?
The following code with a BLOCK construct (Fortran 2008) within an ASSOCIATE construct fails to compile when the associate-name is used inside the block. Is this only to be expected per the standard? I couldn't find anything in the standard that says this is not allowed.
As can be seen in the attached program, when I am trying to open, read and write data into an array, I am getting an error which says as follows:
"forrtl: severe (59): list-directed I/O syntax error".
Any suggestions or insight into this would be greatly helpful.
The Windows C++ Composer XE 2015 Update 2 installer will not let me select "Integration into Visual Studio 2010".
Both Visual Studio 2010 and 2013 are installed on my system, and the installer offers to integrate into 2013, but NOT 2010. The check box is present but "greyed" out. Visual Studio 2010 and 2013 are both fully operational and working fine on my system.
icc 15.0.0 fails to compile the following
here's another bug report about the Coarray implementation of the Intel Compiler (version 15.0.2). The following code fails with a segfault:
Sometimes it is useful, or even necessary(?), to type in compile flags manually in the property field Configuration Properties->Command Line->Additional Options. However, "Additional Options" behave somewhat inconsistently.
I'm getting an "error LNK2001: unresolved external symbol __intel_new_feature_proc_init" with the accompanying LNK1120.
I'm using VS2013 Professional (though I am not!) and just upgraded to Intel Parallel Studio XE 2015 Update 2 yesterday in order to use the OpenMP 4.0 specification that you get with the Intel C++ 15.0 compiler.
Although Visual Studio and other applications appeared to remain in working order after the (very time consuming) Windows Update installation of windows10 tech preview, none of my Intel software tools except Impi came up by themselves. The culprit appeared to be multiple visible versions even though the latest had been installed with the choice to replace the previous. Impi also had 2 visible versions, but that didn't stop it from coming up. Un-installing everything possible and re-installing seemed to recover, but then I had to find a working ifort.cfg elsewhere.