Intel Software Network articles Feed http://software.intel.com/en-us/articles/intel-mkl-kb/type/known-issues/ en-us VML and VSL functions in Intel MKL 10.2 may crash on new processors with old operating systems Reference Number: DPD200261138


Version: Intel® MKL 10.2 (all updates)


Product: Intel® MKL


Operating System: Windows 7 (w/o) Service Pack 1, Windows Vista, Windows XP


Problem Description:

Vector math functions (VML) and Basic Random Number Generator (VSL) functions may crash or hang when run on a CPU that supports Intel® AVX instructions, but has installed an operating system that does not support Intel® AVX instructions.

In version 10.2, Intel MKL had a problem with the code that determines which optimized code-path to take. The dispatcher would test to see if the processor supports AVX instructions, but it did not check for the required support in the operating system. Many of the Intel MKL functions required an additional instruction to 'enable' these code-paths, but the vector math functions (VML) and Random number generators (VSL) functions were unintentionally enabled by default.

Intel AVX instructions are only supported in Windows 7 SP1 and Windows Server 2008 R2 SP1.
They are not supported in Windows Vista or Windows XP.

Linux is supporting Intel® AVX instructions since kernel version 2.6.30 (type 'uname -a' to check).


Resolution Status:

  • All versions since the release of Intel MKL 10.3 (available in Intel® Composer XE 2011) have been fixed.
  • All versions of Intel MKL will work with operating systems that support Intel AVX instructions.
Note:

Please contact us at Intel Premier support or on the User forum if you cannot update your OS or upgrade to a later version of Intel MKL.


[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/vml-and-vsl-functions-issue-on-cpu-types-supported-avx-instruction-set-on-some-of-os-that-do-not-support-intel-avx/ Wed, 02 Nov 2011 15:00:00 -0700 http://software.intel.com/en-us/articles/vml-and-vsl-functions-issue-on-cpu-types-supported-avx-instruction-set-on-some-of-os-that-do-not-support-intel-avx/#comments http://software.intel.com/en-us/articles/vml-and-vsl-functions-issue-on-cpu-types-supported-avx-instruction-set-on-some-of-os-that-do-not-support-intel-avx/ Intel® Math Kernel Library Knowledge Base Issues with use of F77 headers in Intel MKL 10.3.7
Reference Number : DPD200226815


Product : Intel® Math Kernel Library (Intel® MKL)

Version : Intel MKL 10.3.7

Operating System : Windows* operating system

Problem Description : 


Intel MKL for Windows* customers using the following Fortran 77 header files:
  • mkl_dss.f77
  • mkl_pardiso.f77
  • mkl_vml.f77
  • mkl_vsl.f77
  • mkl_rci.fi

and linking their application with the Intel MKL stdcall (or CVF default) library “mkl_intel_s” can get the following linking error:

    "Unresolved external symbols”.

Resolution Status : 


This is a known issue that will be fixed in a future release. To resolve the issue please use the following workaround:

  • Use the corresponding f90 headers instead of the f77 headers
  • Switch to the PGI* F90 compiler if you use PGI* F77





[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

]]> http://software.intel.com/en-us/articles/issues-with-use-of-f77-headers-in-intel-mkl-1037/ Thu, 13 Oct 2011 00:00:00 -0700 http://software.intel.com/en-us/articles/issues-with-use-of-f77-headers-in-intel-mkl-1037/#comments http://software.intel.com/en-us/articles/issues-with-use-of-f77-headers-in-intel-mkl-1037/ Intel® Math Kernel Library Knowledge Base The Intel® MKL 10.3.3 LAPACK functions fail irregularly on Fedora Core 13/RHEL 6 DPD200192968:

The LAPACK functions in Intel® MKL 10.3.3 version fail with Segmentation fault irregularly when linked with libmkl_rt.* on the following configurations:

Intel® Sandy Bridge Processors with Fedora Core 13 or RHEL 6 Operating Systems with installed glibc-2.12.

Since this is a third party issue, we are trying our best to get this addressed as soon as possible.

 

The two workarounds to avoid such segmentation faults, on the above configurations are:

1.     Link Intel® MKL as described at Intel® Math Kernel Library Link Line Advisor (http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor)

-L$(MKLROOT)/lib/intel64  -Wl,--start-group -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -Wl,--end-group -openmp -lpthread

2.     Upgrade your Intel® Sandy Bridge system to Fedora Core 14.

]]> http://software.intel.com/en-us/articles/the-intel-mkl-1033-lapack-fails-on-fedora-13-rhel-6/ Sat, 05 Mar 2011 23:00:00 -0800 http://software.intel.com/en-us/articles/the-intel-mkl-1033-lapack-fails-on-fedora-13-rhel-6/#comments http://software.intel.com/en-us/articles/the-intel-mkl-1033-lapack-fails-on-fedora-13-rhel-6/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Math Kernel Library Knowledge Base *TRMV bug for large problems in threaded operation Reference Number: DPD200165114

Product: Intel® Math Kernel Library (Intel® MKL)

Versions: Intel® Math Kernel Library 10.3 Update 2 and earlier versions with code optimizations for processors based on the Nehalem micro-architecture and later

Operating System: All supported operating systems

Problem description:

The BLAS level 2 functions (*TRMV) which perform the product of a triangular matrix and a vector provide incorrect results when run in threaded mode with matrices of dimension 3000 or larger. The bug is part of a code path which is dispatched on processors based on the Nehalem micro-architecture and later. This includes the Intel® Xeon processors 5500 and 7500 series and the Intel® Core™ i7 processor and those introduced since their introduction.

Workaround:

The problem does not occur when linking the sequential version of the library. The problem does not occur when threading is turned off using any of the means available (see "Managing performance and memory" chapter of the Intel MKL User's guide). For example, you may bracket your calls to DTRMV with calls to mkl_set_num_threads(), temporarily turning threading off for large sizes.

Resolution status:

A fix for this problem is available in Intel MKL 10.3 update 3. ]]> http://software.intel.com/en-us/articles/DTRMV-bug-large-problems-threaded-NHM/ Tue, 01 Feb 2011 00:00:00 -0800 http://software.intel.com/en-us/articles/DTRMV-bug-large-problems-threaded-NHM/#comments http://software.intel.com/en-us/articles/DTRMV-bug-large-problems-threaded-NHM/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Cluster Toolkit for Linux* Knowledge Base Intel® Cluster Toolkit for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Version of Intel(R) MKL compatible with /SAFESEH
Reference Number : DPD200202319


Version : Intel® MKL 10.3.Update1 and earlier


Product : Intel(R) Math Kernel Library (Intel MKL)


Operating System :  Windows


Problem Description :

While building the code on Windows 32 bits with Visual Studio 2005 or 2008 using /SAFESEH linker option ( see the details follow the link:”
http://msdn.microsoft.com/en-us/library/9a89h429(v=VS.80).aspx” and linking against MKL static libraries – you will get a lot of errors like:
mkl_core.lib(_p4m_xdcopy.obj) : error LNK2026: module unsafe for SAFESEH image.
mkl_core.lib(_avx_zr4irev.obj) : error LNK2026: module unsafe for SAFESEH image.
mkl_core.lib(_p4m3_zrad4if.obj) : error LNK2026: module unsafe for SAFESEH image.
..............
..............


Resolution Status :
The problem has been already fixed and available in the versions of Intel(R) MKL 10.3 Update 2 released this week.


[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/version-of-intelr-mkl-compatible-with-safeseh/ Mon, 31 Jan 2011 13:00:00 -0800 http://software.intel.com/en-us/articles/version-of-intelr-mkl-compatible-with-safeseh/#comments http://software.intel.com/en-us/articles/version-of-intelr-mkl-compatible-with-safeseh/ ISN General Intel® Math Kernel Library Knowledge Base MKL CFFT examples fail with MPICH2 on Windows* Itanium machine
Reference Number : 
DPD200198806


Version : 
Intel® MKL 10.2.4 and later

Product : 
Intel® Math Kernel Library

Operating System : 
Microsoft Windows*

Problem Description : 

CFFT examples in Intel MKL fail with MPICH2 on Windows Itanium machine. The route cause for this problem is that MPICH2 (mpiexec.exe) does not process values of environment variables (e.g. PATH) longer than 260 characters (MAX_PATH defined in windef.h).

Starting with Intel® MKL 10.2.4 examples were compiled/linked with /Qopenmp which caused threading libs conflict with 10.1 compiler.


Resolution Status : 

The fix for this is avaialble in MKL 10.2.7, and examples were changed to follow Intel’s recommendation to use dynamic OpenMP libraries (libiomp5.dll). The MKL binaries are not modified, hence current customers’ applications are not impacted.

As a workaround for now, we recommend the below two options now.

1. Make sure your PATH is shorter than 260 characters or set your system PATH to include required paths.

2. Copy all dependant DLLs to the folder which contains the executable.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/mkl-cfft-examples-fail-mpich2-windows-itanium/ Wed, 08 Dec 2010 07:30:00 -0800 http://software.intel.com/en-us/articles/mkl-cfft-examples-fail-mpich2-windows-itanium/#comments http://software.intel.com/en-us/articles/mkl-cfft-examples-fail-mpich2-windows-itanium/ Intel® Math Kernel Library Knowledge Base How to select different update of Intel® Composer XE 2011 for Linux* and Mac OS* X Reference Number : dpd200194608, dpd200160631

Version : 2011 (Compiler 12.0)

Product : Intel Composer XE 

Operating System : Linux, Mac OS X


Problem Description :  When an Intel Composer XE update is installed, the scripts compilervars.sh [.csh] in the bin directories of previously installed compilers no longer set the environment for the corresponding compiler or update, but set the environment for the most recent update instead. This applies to all components of Intel Composer XE that may be present: C/C++ and Fortran Compilers; Intel Debugger; Intel Threading Building Blocks; Intel Math Kernel Library and Intel Performance Primitives.


Workaround: 
To select a compiler update other than the latest, please use the script compilervars_arch.sh [.csh] from the bin directory of the desired compiler version. Similarly, for other components of Intel Composer XE, use the scripts idbvars.sh, tbbvars.sh, mklvars.sh and ippvars.sh from the bin directory of the desired version, as needed.

Resolution Status:
The issue has been fixed in Composer XE update #4.  To select a specific version, use the compilervars.[c]sh script from the version-specific directory.  For example, after installing update #4 on a system where update #3 was already installed:

> source /opt/intel/composerxe-2011.3.174/bin/compilervars.sh intel64  <<<=== update #3

> ifort -V
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 12.0.3.174 Build 20110309

> source /opt/intel/composerxe-2011.4.191/bin/compilervars.sh intel64 <<<== update #4

> ifort -V
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 12.0.4.191 Build 20110427

As before, the script from the generic, non-version specific directory will initialize for the most recent update:

> source /opt/intel/composerxe-2011/bin/compilervars.sh intel64  <<<=== non-version specific (most recent update)
> ifort -V
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 12.0.4.191 Build 20110427





[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/how-to-select-different-update-of-intel-composer-xe-2011-for-linux-and-mac-os-x/ Mon, 06 Dec 2010 08:00:00 -0800 http://software.intel.com/en-us/articles/how-to-select-different-update-of-intel-composer-xe-2011-for-linux-and-mac-os-x/#comments http://software.intel.com/en-us/articles/how-to-select-different-update-of-intel-composer-xe-2011-for-linux-and-mac-os-x/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Integrated Performance Primitives Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Threading Building Blocks Knowledge Base Information about the FTC Decision and Order on the Intel® Compilers Reimbursement Fund www.CompilerReimbursementProgram.com, for further information. ]]> http://software.intel.com/en-us/articles/information-about-the-ftc-decision-and-order-on-the-intel-compilers-reimbursement-fund/ Mon, 01 Nov 2010 00:00:00 -0700 http://software.intel.com/en-us/articles/information-about-the-ftc-decision-and-order-on-the-intel-compilers-reimbursement-fund/#comments http://software.intel.com/en-us/articles/information-about-the-ftc-decision-and-order-on-the-intel-compilers-reimbursement-fund/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Software Development Tool Suites for Intel® Atom™ Processor Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Integrated Performance Primitives Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Errors linking Intel® compilers with Intel® MKL 10.x

Symptoms

When building with Intel® Math Kernel Library for Windows* version 10.0 using the xilink linker from the command line or within the Microsoft Visual Studio* IDE, the following error messages may occur:

Severe: **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.
Link: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 3)
Link: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 3) or(0): internal error: backend signals
xilink: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 4)
xilink: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 4)

When using the Intel® C++ Compiler for Windows*, these errors have occurred when the /Qipo compiler option is used with the xilink linker from the command line.

When using the Intel® Visual Fortran Compiler for Windows*, these errors have occurred when building within the Visual Studio IDE, which uses the xlink linker.

Solution

Intel® Math Kernel Library for Windows version 10.0 introduced new library naming conventions, with "dummy lib" references to the older Intel® MKL libraries and were given for backward compatibility. However, there is a format problem with the Intel MKL "dummy libs" files that is causing problems for the Intel xilink tool. Correct the problem by modifying link information for the command line or the Visual Studio link information to specify the new names of the 10.0 Intel MKL libraries.

The dummy or compatibility libraries have been removed from Intel® MKL 10.2 or later versions, and if you using one of the latest versions, this error will not occur.

Linking from the Command Line

When link errors occur, correct the problem by replacing references to the Intel MKL dummy libraries on the link command with explicit references to the libraries listed in the dummy libraries. See the explicit Intel MKL library references listed below.

Linking from within Microsoft Visual Studio

In the Visual Studio IDE, replace the references to the dummy libraries in Project » Configuration Properties » Linker &» Input » Additional Dependencies. See the explicit Intel MKL library references listed below.

For IA-32 Compilers
Intel MKL dummy library Replace with explicit Intel MKL library references
mkl_c_dll.lib mkl_intel_c_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib
mkl_s_dll.lib mkl_intel_s_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib
mkl_c.lib mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib
mkl_s.lib mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib
mkl_scalapack_dll.lib mkl_scalapack_core_dll.lib
mkl_scalapack.lib mkl_scalapack_core.lib
mkl_cdft_dll.lib mkl_cdft_core_dll.lib
mkl_cdft.lib mkl_cdft_core.lib
For Intel® 64 Compilers
Intel MKL dummy library Replace with explicit Intel MKL library references
mkl_dll.lib mkl_intel_lp64_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib
mkl_em64t.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib.lib
mkl_scalapack_dll.lib mkl_scalapack_lp64_dll.lib
mkl_scalapack.lib mkl_scalapack_lp64.lib
mkl_solver.lib mkl_solver_lp64.lib
mkl_cdft_dll.lib mkl_cdft_core_dll.lib
mkl_cdft.lib mkl_cdft_core.lib
For IA-64 [Intel® Itanium®] Compilers
Intel MKL dummy library Replace with explicit Intel MKL library references
mkl_dll.lib mkl_intel_lp64_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib
mkl_ipf.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib
mkl_scalapack_dll.lib mkl_scalapack_lp64_dll.lib
mkl_scalapack.lib mkl_scalapack_lp64.lib
mkl_solver.lib mkl_solver_lp64.lib
mkl_cdft_dll.lib mkl_cdft_core_dll.lib
mkl_cdft.lib mkl_cdft_core.lib
]]> http://software.intel.com/en-us/articles/performance-tools-for-software-developers-errors-linking-intel-compilers-with-intel-mkl-10x-dummy-libs/ Sun, 31 Oct 2010 08:30:00 -0700 http://software.intel.com/en-us/articles/performance-tools-for-software-developers-errors-linking-intel-compilers-with-intel-mkl-10x-dummy-libs/#comments http://software.intel.com/en-us/articles/performance-tools-for-software-developers-errors-linking-intel-compilers-with-intel-mkl-10x-dummy-libs/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Dynamic MKL OOC PARDISO cannot solve large problem on Win64 bit OS.
Reference Number : DPD200193362


Version : 10.2 Update 6, 10.3 beta 2


Product : Intel(R) Math Kernel Libary


Operating System : Windows, 64 bits


Problem Description :
During solution of pretty big tasks with OOC mode of PARDSIO on Win64 OS ( Win7 )
with Dinamic linking mode

PARDISO generates the next report:
Fseek failed
*** Error in PARDISO ( numerical_factorization) error_num= -987
*** Error in PARDISO: zero pivot

The issue happens independently of type of solved matrixes.

Root Cause:
This problem occurs because of there is unresolved reference _fseeki64 into dynamic libraries of Intel(R) MKL on Win64 OS.

Workarounds:
Using statically linking mode instead of dynamic.

Resolution Status :
the fix of this issue will available the next versions: 10.2 Update 7 and 10.3 



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/dynamic-mkl-ooc-pardiso-cannot-solve-large-problem-on-win64-bit-os/ Thu, 30 Sep 2010 11:30:00 -0700 http://software.intel.com/en-us/articles/dynamic-mkl-ooc-pardiso-cannot-solve-large-problem-on-win64-bit-os/#comments http://software.intel.com/en-us/articles/dynamic-mkl-ooc-pardiso-cannot-solve-large-problem-on-win64-bit-os/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Cluster Toolkit for Windows* Knowledge Base Intel® Math Kernel Library Knowledge Base