I used to have on my old computer the Intel Visual Fortran Composer XE 2011, integrated with Microsft Visual Studio 2010, and with IMSL 6.
Now I have upgraded to the Intel Parallel Studio XE Composer Edition for Fortran Windows* with Rogue Wave* IMSL* 7.0.
What is happening is that now, some of my Fortran programs are not compilling. It gives me the following error:
fatal error LNK1104: cannot open file libucrt.lib
Do you know why this happens? can you help?
The MERGE function seems to use temporary arrays for both, tsource and fsource, arguments when the program is compiled in the Debug mode. Hence, the following simple code throws an exception:
I'm running Windows 8.1 pro, and installed Microsoft Visual Studio 2013 update 5
I'm trying to install Intel Parallel Studio XE 2015 Update 1 Composer Edition for Fortran and C++ but i Faced with error 1603
The following test program gives incorrect results when options such as /Ot, /O2, /fast are used on Windows 8.1 with the 32 and 64-bit IFort compiler version 184.108.40.206. Some earlier versions of the compiler, such as 11.1.070, give correct results whether or not optimization is requested.
Hi, I wondered if anyone had used the Intel codecov tool for analysis of a static library.
I am building a static library comprising mainly algorithmic content which I want to analyse and also have a driver program which is used to test the library. The driver is linked against a static .lib. If I follow the examples in the documentation and compile everything with /Qcov-gen I get a dyn file in the exe directory and when I use the tools on that it gives me coverage analysis for the exe not for the library. However it is the library I am most interested in.
HI Lorri, others,
I have just one more question before I dive in and try to play
with rewriting parts of my application for threadsafe, and it
relates to reading the input data.
Each thread independently processes in the same way , without any sharing
of results between the threads, data from the single data file submitted to the thread.
The file is identified by a full path, such as c:\mydatafiles\exmpl001.dat as the first argument from the c== calling interface