The complexity of System-On-Chip based designs used in Intelligent Systems is growing fast with platforms comprised of multiple different cores with the software stack interacting across these cores. This translates directly to a more complex software stack, that has its own challenges for guaranteeing consistent reliability throughout the devices life cycle. Thus it is ever more important to have system and application debug solutions that provide deep hardware and platform insight as well as visibility of the entire system software stack.
This page provides the current Release Notes and Getting Started Documents for the Intel® System Studio 2014 product.
This page is current as of Intel® System Studio packages l_cembd_p_2014.0.025 (Linux* host) and w_cembd_2014.0.026 (Windows* host).
To get product updates, log in to the Intel® Software Development Products Registration Center.
For questions or technical support, visit Intel® Software Products Support.
We have a number of customers report regarding incorrect behavior of GELS in Intel® MKL 11.0 if sequential library is linked.
Customer’s quote:”When I compile and run this program with Intel® Fortran Composer XE 2013(**), the output is totally wrong. Compiling and running with Intel FORTRAN Composer XE 2011 (*) gives the correct results.”
Problem Description: Statically linking MKL and IPP in the same project produce the link errors like the following:
1>ipps_l.lib(pscopyg9as_g9.obj) : error LNK2005: _g9_ownsSet_32s_G9 already defined in mkl_core.lib(pscopyg9as_20120907.obj)
1>ipps_l.lib(pscopyg9as_g9.obj) : error LNK2005: _g9_ownsSet_16u_G9 already defined in mkl_core.lib(pscopyg9as_20120907.obj)
1>ipps_l.lib(pscopyg9as_g9.obj) : error LNK2005: _g9_ownsSet_8u_G9 already defined in mkl_core.lib(pscopyg9as_20120907.obj)