Intel Software Network articles feed

Redistributable libraries for the Intel(R) C++ and Visual Fortran Compiler for Windows

Wed, 14 Oct 2009 10:13:19 -0700

Overview

This article contains links to the redistributable installation packages for the Intel Compiler Professional Editions for Windows.

The redistributable packages are for the end users who use applications that are built with Intel Compilers. Please note that there is one redistributable package for every compiler update. Make sure you download and install the one recommended by the application vendor.

OS requirement for redistributable packages for Intel Compiler Professional Editions for Windows 11.1

The supported OS are: Windows XP*, Vista*, Windows Server 2003*, Windows Server 2008*, Windows HPC Server 2008*.

Installation instructions

The installation program of the redistributable package will guide you through the installation. You will need to accept the license and the installation will install all the libraries to the fixed directory.

For the redistributable package of Intel C++ Professional Compiler for Windows, the installation directory is
[Common Files]\Intel\Shared Files\cpp

For the redistributable package of the Intel Fortran Professional Compiler for Windows, the installation directory is
[Common Files]\Intel\Shared Files\Fortran

The installation will add the above directory to your environment variable "path" as well.

If you wish to install the redistributable package "silently", so that no output is presented to the user, run the executable with the following options added to the command line like:
>> w_cproc_p_11.1.04x_redist_xxx.exe /S /V/qn

Links to the redistributable packages

Intel C++ Compiler for Windows 11.1.048 (update 2 revised) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64	Intel Visual Fortran Compiler for Windows 11.1.048 (update 3) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64
Intel C++ Compiler for Windows 11.1.051 (update 3) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64	Intel Visual Fortran Compiler for Windows 11.1.051 (update 3) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64

References

Redistribution of Application Binaries Built for Microsoft* Windows

Changing Language Setting to see English on a Japanese OS environment or Vice Versa on Windows

Mon, 14 Sep 2009 10:15:23 -0700

The Intel C++ and Fortran Compiler for Windows 11.1 update 2 release provide localized Japanese message catalog.

The installation of Intel Compiler for Windows will install both English message catalog and Japanese message catalog on your system. Installation directories are:

<...>\1033 for English
<...>\1041 for Japanese

Steps to see Japanese message on an English development system: English OS, English Visual Studio*.

open "Regional and Language Options" dialog from "Control Panel"
under "Advanced" tab, change the "Language for non-Unicode programs" to "Japanese" like following:

click on "Apply". This change requires "Reboot"
after "Reboot", you should see the diagnostic message in Japanese from the command line build environment or from within the Visual Studio* IDE.

Steps to see English message on a Japanese development system: Japanese OS, Japanese Visual Studio*.

open "Regional and Language Options" dialog from "Control Panel"
under "Advanced" tab, change the "Language for non-Unicode programs" to "Japanese" like following:
click on "Apply". This change requires "Reboot"
after "Reboot", you should see the diagnostic message in Japanese from the command line build environment or from within the Visual Studio* IDE.

Intel C++ or Fortran Compiler for Windows Silent Installation Guide

Mon, 31 Aug 2009 12:09:05 -0700

Introduction: This article describes how to perform a "silent" (non-interactive) install of Intel C++ Compiler for Windows or Intel Visual Fortran Compiler for Windows. It applies to version 11.1; it is not applicable to earlier versions of the product. An administrator may wish to use a silent install to make the product available in an automated fashion on users systems.

Other Silent Install articles:

Intel C++ and Fortran Compilers for Linux Silent Install Guide

Step 1

If you are installing from a downloaded product package (file type .EXE), you must unpack the package to a convenient directory on your (adminisrator's) system or to a network share. The simplest way to do that is to run the EXE and specify the path for where the files should be unpacked. This is done with the following dialog (Fortran example shown, C++ is similar):

Click the Extract button to do the extraction. When the setup reaches the Welcome screen, click Cancel to exit the installation.

Step 2

Either copy the installation file tree to the target system or reference it from a network share. On the target system, from an account with Administrator privilege, run the setup.exe in the unpacked folder with the required arguments. Note that if the path to setup.exe includes blanks, you must enclose the file path in quotes, for example:

"E:\Unpacked Files\Intel\w_cproc_p_11.1.038\setup.exe"

or

"E:\Unpacked Files\Intel\w_cprof_p_11.1.038\setup.exe"

The form of the silent install command is:

setup.exe install argument [argument]...

Where each argument is described in sections below. The command invoking setup.exe will return immediately.

Required arguments:

--output=filespec

This specifies the path to the file where output from the install will be directed. If the path is not complete, it will use the path to setup.exe as a default.

--eula=accept | reject

This specifies whether you accept or reject the End User License Agreement. If reject is specified, the installation will exit.

Optional arguments:

--installdir=path_for_installation_folder

Specifies a path for the installation folder. If not specified, the default is used. Please read the compiler Release Notes for details.

--license-path_to_license_file

Specifies the path to the license file to be used on this system. The file should have a file type of .LIC, or you may specify a folder path and the installer will examine all .LIC files in that folder for an appropriate license. If you do not specify either --license or --sn, the installer will look on the system to see if an appropriate license already exists.

--sn=serial_number

Specifies the serial number for the license to be used on this system. Use either --sn or --license, not both. The serial number is in the form xxxx-xxxxxxx. If --sn is used, a network connection to the Internet must be available during installation.

--update=no | always

Specifies the behavior if the product is already installed. "no" will end the installation if the current version (any update) is installed. "always" will remove the latest version before installing the new one. The default is "no".

Example command

"E:\Unpacked Files\Intel\w_cprof_p_11.1.038\setup.exe" install --output=C:\Logs\log.txt --sn=ABCD-1234567

Tips for using PARDISO

Fri, 28 Aug 2009 16:12:50 -0700

Introduction

The interface to the PARDISO solver has many parameters and learning to use it for the first time can take a lot of time. The DSS interface for PARDISO was created to provide a simpler interface to the functionality, but often users still want to use the PARDISO interface. This article provides some tips for getting started and corrects some of the mistakes made by first-time users and even occasionally by experienced users.

General tips

Explore the examples in the examples/solver directory of MKL. By choosing an example program that solves a problem that is close to the sort of problem you will be solving you can get to know some of the most helpful and relevant parameter settings for your case.

Use the matrix checker: The iparm(27) parameter of PARDISO controls the input checker. By default it is turned off (iparm(27)=0), so you'll need to turn it on by setting iparm(27)=1. PARDISO will run some checks on your data structure and return an error message if it finds that something was wrong. This can help you find simple errors in your indexing as well as correct misunderstandings about how PARDISO expects your matrix to be represented and stored (e.g., a symmetric matrix should be stored in upper triangular form).

Check your link line:Sometimes a program linked against Intel MKL can misbehave (crash, hang, etc.) because the program was linked against the wrong threading layer (which assumes a specific threading runtime) or wrong interface (e.g., ILP64 v. LP64; cdecl v. stdcall). The link line advisor may be helpful if you're using the latest version of Intel MKL. For earlier versions you should consult the Intel MKL User's Guide chapter 5 on linking your application.

Important settings

Use message level information: The solver prints statistical information to the screen if the input parameter msglvl = 1 and generates no output if msglvl = 0. There is no default value for this option.

Single and double precision: Starting version 10.2 Intel® Math Kernel Library supports computations in single precision as well as double precision. To switch between single and double precision modes you should use iparm(28). The default mode of iparm(28) is 0, which corresponds to the double precision. If iparm(28) = 1 all internal computations are made in single precision. Please refer to this article for more information on these options.

Use default values: To get started quickly with PARDISO you can use the default values for each of the elements in the iparm array. Setting iparm(1) = 0 will cause PARDISO to use the default values for the rest of the array: iparm(2) and iparm(4) through iparm(64). Otherwise, you must supply all the values in the iparm array.

Rewrite the solution: if you need to store the output solution on the right hand side of array b, choose iparm(6) = 1.
The default value of iparm(6)=0, which corresponds array x contains the solution.

Other sources of information

If you're still having trouble and/or you suspect you've found a problem in Intel MKL, you might check the known issues article in the Intel MKL knowledgebase. Another option is to search the Intel MKL forum for other reports of a similar problem or post a question of your own.

Troubleshooting Fortran Integration Issues with Visual Studio

Fri, 14 Aug 2009 12:03:52 -0700

This article describes diagnostic and repair steps to follow if Intel Visual Fortran integration into Microsoft Visual Studio is not working correctly.

The symptoms of errors with Fortran integration into Visual Studio include:

When opening a Fortran project, an error indicating that the .vfproj project file is not recognized
Missing Fortran-specific parts of the Visual Studio interface, such as project templates or project properties
Inability to build a Fortran project

This article applies to Intel Visual Fortran 10.0 through 11.1 with Microsoft Visual Studio 2003, 2005 or 2008.

Step 1 - are prerequisites met?

Open Microsoft Visual Studio from the Start menu. Select Help > About. Look for the following items:

In Visual Studio 2005 and 2008, make sure that it does not say "Express Edition". Visual Studio Express Edition is not supported for use with Intel Visual Fortran from within the Visual Studio development environment
If you are using a Standard, Professional or Team System Edition of Visual Studiom under Installed Products, look to see if "Microsoft Visual C++" is listed. If it is not, reinstall Visual Studio and make sure that the Visual C++ component is installed. If you are using the Microsoft Visual Studio 2005 Premier Partner Edition (included with Intel Visual Fortran 10.0, 10.1 and 11.0 - no edition name will be displayed), or Microsoft Visual Studio 2008 Shell (included with Intel Visual Fortran 11.1), Visual C++ is not required
Look under Installed Products to see if "Intel Visual Fortran Compiler Integration" is listed and make a note of the version number or "Package ID" displayed, if any.

Close Visual Studio

Step 2 - are the integration files present?

Check to see if the appropriate Intel folder is present. The paths given here are defaults and may vary on your system:

VS2003: C:\Program Files\Microsoft Visual Studio .NET 2003\Intel Fortran\VFPackages
VS2005: C:\Program Files\Microsoft Visual Studio 8\Intel Fortran\VFPackages
VS2008: C:\Program Files\Microsoft Visual Studio 9.0\Intel Fortran\VFPackages

Check to see if this folder contains six DLL files Windows may hide the file type for DLL files - the file names are VFAVwin.dll, VFFortSvc.dll, VFHieEditor.dll, VFProj.dll, VFProjConvert.dll, VFToolOpt.dll. If any of these files are not present, uninstall and reinstall Intel Visual Fortran.

Right click on VFProj.dll and select Properties, then click on the Version tab. Look at the "File Version" displayed. It will be in the form of 11.1.3464.2008. The first two numbers (11.1 here) indicate the compiler version. These must match that of the most recent version of the compiler installed. The last number (2008 here) indicates the Visual Studio version this DLL is for. If the compiler version does not match, uninstall Intel Visual Fortran, delete the entire "Intel Fortran" folder under the appropriate Microsoft Visual Studio folder, then reinstall Intel Fortran.

Step 3 - run the repair tool

If the above steps do not resolve the problem, download the appropriate ZIP file indicated below and run the executable file included within. Note: If you are running Windows Vista, Windows 7 or Windows Server 2008, run the program by right clicking it and selecting "Run as Administrator". In many cases, this will resolve the problem. If it does not, or if an error during registration of a DLL is noted, contact Intel Support for further options.

VS2003 Repair Tool
VS2005 Repair Tool
VS2008 Repair Tool

[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.]

How am I notified of updates for my registered products?

Mon, 10 Aug 2009 00:40:04 -0700

Problem :
How am I notified of updates for my registered products?

Resolution :
1) Login to the Intel® Registration Center by entering your Login ID and Password in the Registered Users Login section of the web page. You will see a list of all products you have subscribed;
2) Click on My account/Change notification preference on My products page below.

3) You will be directed to the page below, check the box of Yes, I would like to receive Intel® Software Product update notifications.

4) Click Save Notification Prefences.

You will then receive the registered product update notifications.

How to build MKL application in Intel Visual Fotran (MSVC*2005)

Mon, 03 Aug 2009 01:50:56 -0700

Software Requirement:
1. Intel® Visual Fortran Compiler Professinal for Windows.
The compiler were requied to installed and intergated to Microsoft VC 2005 or VC 2008 correctly.

2. Intel® MKL for windows
   You can install MKL seperately or install the intergarted MKL when install Intel Fortran Compiler Professional version.

3. Microsoft* Visual Studio 2005 or 2008.
For who'd like to build x64 bit appliation, please install the MSVC* package which supports X64 development.

Step1 : Which kind of application: ia32, em64t or ia64 application you need to build?
Which target machine you need your application run on?
ia32: 32 bit application.
EM64t: Intel 64 bit application
IA64: Intel Itanium 64bit application.

Most of us may build ia32 or em64t application on a xeon machine with windows*. Then in MSVC* environment, please check the project configuration manager=> active platform. They should be "ia32" or "X64" (which is corresponding to em64t).

Step 2 : Which MKL library you need link against?
2.1) please check the on-line KB article Intel® Math Kernel Library Link Line Advisor After choose it, you can get which libraries you need to list.

For example,
"mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib" are enough for a ia32 windows application generally.
"mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib" are ok for a X64 windows appliation

Step 3: How to link MKL in your project manually?
3.1)  Please follow the steps in how to use MKL in MSVC to add the include path, library path and mkl library as the article show.

For example, add include path manually

please take care of about library path, you need enter right directory:
\ia32, for ia32 application
\em64t, for X64 application
\ia64, for IA64 application
they can't be mixed.

Step 4: How to link MKL in your project automatically - One Button Support (optional)
The recent MKL version have provided one "build" menu in MSVC environment. Click one button, all of environment setting and required library are ready in your project.
* This step can replace the step3 in most of case.
Or if the button is not show, please try step3, set the paths and library manually.
4.1) See below sreencopy in MSVC 2005, click the version you need

Then the required library will be added in your project automatically.

4.2) In Visual Fortran compiler, it is a little different, to integrate MKL, please click the compiler option as below, change the "No" to value like /Qmkl:parallel or /Qmkl:sequential

Please note: some interface libraries (i.e mkl_lapack95.lib mkl_blas95.lib fftw3xc_ms) are not MKL standard library, so the "one button" integration don't support it. You may add them manually if you need to use them.

Step 5: About Compaq*Visual Fortran support and porting from 32bit to 64bit (Optional for who have used CVF)
CVF and Intel Fortran compiler use different call convention by default:
CVF: stdcall
Intel Fortran, C Compiler: cdecl (default interface of the Microsoft Visual C* application)

5.1) MKL support both of them on ia32 platform, but if you are porting from CVF to intel Fortran, you may take care of the required library: mkl_intel_s or mkl_intel_c.lib

Using the CVF compiler
The CVF compiler will link with mkl_intel_s[_dll].lib if routines are compiled with the default interface. However, if you compile with the option /iface=(cref,nomixed_str_len_arg), the compiler will link with mkl_intel_c[_dll].lib .
Using the Intel® Fortran compiler
The Intel Fortran compiler will link with mkl_intel_c[_dll].lib by default. But if the /Gm option is used, call mkl_intel_s [_dll].lib (/Gm enables CVF and Powerstation calling convention compatibility, so does /iface:cvf).

5.2) MKL don't provide em64t and IA64 CVF interface support. So if you are porting CVF 32bit application to X64 or IA64 platform with Intel Fortran compiler and MKL. Please note, you must to link "mkl_intel_lp64|ilp64, mkl_intel_thread, mkl_core.lib" and remove the compiler option /Gm or /iface:cvf.

Here is a MSVC 2005 project (Intel fortran 11.0.0.074 IA32 application) for your reference.DFT_VF_sample.zip

Troubleshooting
When build the project,
1. fatal error LNK1104: cannot open file 'mkl_xxx.lib'
please make sure the library is in the library path and the path you marked in step 3 or step 4 are right one

2. "error #7002: Error opening the compiled module file. Check INCLUDE paths. [MKL_DFTI]."
Please add the header file mkl_dfti.f90 in your code, for example,

! Include to build module MKL_DFTI
INCLUDE 'mkl_dfti.f90'
before the code line
USE MKL_DFTI

Or copy the mkl_dfti.f90 file to the source directory of your project and include it in your Project.

How to Compile for Intel® AVX

Thu, 16 Jul 2009 16:34:04 -0700

Intel® AVX (Intel® Advanced Vector Extensions) is a 256 bit instruction set extension to Intel® SSE (Intel® Streaming SIMD Extensions) that was first announced in 2008. Further information about Intel AVX is available at http://software.intel.com/en-us/avx/ .

The Intel C/C++ and Fortran Compilers, version 11.1, support the building of applications for Intel AVX. On Windows*, use the command line switch /QxAVX. On Linux*, use –xavx. The switches /QaxAVX (Windows) and –axavx (Linux) may be used to build applications that will take advantage of AVX instructions on Intel systems that support these, but will use only SSE instructions on other systems.

Both C/C++ and Fortran compilers support automatic vectorization of floating-point loops using AVX instructions. The C/C++ compiler also supports AVX-based intrinsics (via the header file immintrin.h) and inline assembly. Intel AVX allows the vectorization of a wider variety of floating point loops than Intel SSE, with a greater potential performance gain due to the greater width of the SIMD registers. The vectorizer is enabled automatically by the switches listed above. To see which loops have been vectorized, use the switch /Qvec-report1 (windows) or –vec-report1 (Linux).

Pending availability of processors supporting Intel AVX, the Intel® Software Development Emulator (Intel® SDE) is available for testing programs built for Intel AVX. See http://software.intel.com/en-us/articles/intel-software-development-emulator/ .
Further general information about the Intel Compilers for C/C++ and Fortran is available at http://software.intel.com/en-us/intel-compilers/ . Further information about compiler support for Intel AVX may be found in the Intel C++ Compiler User and Reference Guides, for example in the section 'Intrinsics for Advanced Vector Extensions', accessible online at http://software.intel.com/sites/products/documentation/hpc/compilerpro/en-us/cpp/win/compiler_c/index.htm .

Redistribution of Application Binaries Built for Microsoft Windows*

Fri, 10 Jul 2009 16:50:43 -0700

Applications built with 11.x Intel® Compiler Professional Editions or with Intel® Parallel Composer may be installed on systems where the Intel Compiler Professional Edition or Intel Parallel Composer is not installed. This document provides help for application developers to build the redistribution kit.

Beginning with 11.0, the Intel Compiler Professional Editions is a fully integrated product; in contrast, the 10.x Intel Compiler Professional Edition licenses “bundled” separate component products.

The 11.x Intel® C++ Compiler Professional Edition for Windows* products include the Intel® C++ Compiler, the Intel® Math Kernel Library, the Intel® Integrated Performance Primitives, and the Intel® Threading Building Blocks products.

The 11.x Intel® Visual Fortran Compiler Professional Edition for Windows* products include the Intel® Visual Fortran Compiler with the Intel® Math Kernel Library.

The 11.x Intel® Visual Fortran Compiler Professional Edition for Windows* with IMSL* products include the Intel® Visual Fortran Compiler, the Intel ® Math Kernel Library and the IMSL Fortran Numeric Library* from Visual Numerics.

The attached PDF document includes information on redistributable libraries for all the component products included with Intel Compiler Professional Editions for Microsoft Windows*.

11x_Redistribution_FAQ_Windows.pdf

Due to the many differences in redistributing applications built for Microsoft Windows* vs. Linux* vs. Mac OS* X, a separate redistribution article is provided in Intel® Software Knowledge Base for each OS for Intel Compiler Professional Edition products (Microsoft Windows*, Linux* and Mac OS* X) and for Intel Parallel Composer. The Knowledge Base article at the following link includes information on redistributable libraries for all the component products included with Intel Parallel Composer:

http://software.intel.com/en-us/articles/faq-intel-parallel-composer-redistributable-package/

The Knowledge Base article at the following link includes information on redistributable libraries for all the component products included with Intel® Compiler Professional Editions for Linux*:

http://software.intel.com/en-us/articles/redistribution-of-application-binaries-built-for-linux/

The Knowledge Base article at the following link includes information on redistributable libraries for all the component products included with Intel® Compiler Professional Editions for Mac OS* X:

http://software.intel.com/en-us/articles/redistribution-of-application-binaries-built-for-mac-os-x/

Fortran Real Literal Constants Are Single Precision

Thu, 02 Jul 2009 13:23:20 -0700

Fortran real literal constants are by default single precision. It is important that care is taken when assigning a literal to a quad precision or double precision variable so that you get the expected results.

For example, consider these two assignments to B:

B = 3.1
B = 3.10000000000

If B is defined as double or quad precision, the literal constant is not. If you intend to B to contain or double or quad precision value, you need to write:

B = 3.1_8 for double precision

OR

B = 3.1_16 for quad precision

Alternatively to using the notation above, you can use compiler options /real-size:64 (double precision) or /real-size:128 (quad precision). The Windows compiler options are listed. Please see the compiler documentation for Linux* and Mac OS X* compiler options.

These are just two of many ways to set precision of real literal contants. For additional methods please consult a Fortran programming language reference manual.