• English

• English

• English

• English

• English
• Japanese

• English

• English
• Japanese

Linux Compiler Professional 11.1
"Silent" or "Non-interactive" Installation Instructions

Contents:

• Silent Command Line Installations
• RPM Command Line Installations
• LSB Support
• Redistribution Package Installations
• Uninstall Instructions
• Links of Interest

Silent Command Line Installations

Starting with release 11.0, the Linux installation programs for Compiler Professional are built using the PSET (Program Startup Experience Technologies) 2.0 core.  This PSET core is a framework of tools built by Intel to provide a robust set of installation and licensing features that are consistent across Intel product lines.  A similar PSET core is used for the Windows* and Mac OS* X installation packages as well.

One feature provided in the PSET core is support for the "silent" install.  Historically, "silent" really meant "non-interactive".  At this point, "silent" also means "does not report copious amounts of information".  The silent install really is silent now, assuming there are no problems during the installation.  The silent install method allows the user to perform a command line installation of an entire package with no need to answer prompts or make product selections.

A historical note specific to Linux installs: there has been a "silent" install capability in the Linux Compiler products since version 9.0.  This legacy version, included in versions 9.1, 10.0, 10.1, and 11.0 as well, performed the same function.  But starting with version 11.1, the legacy silent install embedded in the "inner install components" has been removed.  The new PSET core silent install is the only method still supported - that is, older silent installation tools in v11.0 and older are no longer supported other than the RPM command line install method (see details on RPM-based installs below).

Silent Install Steps: "From Scratch"

To run the silent install, follow these steps:

• Make sure that a working product license is in place before beginning.  The file should be world-readable and located in a standard Intel license file directory, such as /opt/intel/licenses.
  
• Create / edit a silent install INI file.  Here is an example file.  A similar file can be edited and placed in any directory on the target system.

ACTIVATION=exist_lic
CONTINUE_WITH_INSTALLDIR_OVERWRITE=yes
CONTINUE_WITH_OPTIONAL_ERROR=yes
PSET_INSTALL_DIR=/opt/intel/Compiler/11.1/038
INSTALL_MODE=RPM
ACCEPT_EULA=accept

• Run the silent install.  For example, if you untarred your compiler package in /tmp for version 11.1.038:

prompt> cd /tmp/l_cproc_p_11.1.038

prompt> ./install.sh --silent /tmp/my_silent_config.ini

prompt>

That's it! The silent install is complete.

A few comments on the fields inside the silent install INI file:

• ACTIVATION=exist_lic

This tells the install program to look for an existing license during the install process.  This is the preferred method for silent installs.  If you have only a serial number, please visit https://registrationcenter.intel.com to register your serial number.  As part of registration, you will receive email with an attached license file.  Save the license file in /opt/intel/licenses/ directory.  If you have already registered your serial number but have lost the license file, revisit https://registrationcenter.intel.com and click on the hyperlinked product name to get to a screen where you can cut and paste or mail yourself a copy of your registered license file.

• CONTINUE_WITH_INSTALLDIR_OVERWRITE=yes

This tells the installer that it is OK to write into an existing directory.  This should be set to "yes" especially in the case where a C/C++ installation will be written into the same major product tree as a Fortran installation from the same packaging cycle (e.g. l_cproc_p_11.1.038 and l_cprof_p_11.1.038).

• CONTINUE_WITH_OPTIONAL_ERROR=yes

This tells the install program that if the optional, non-critical prerequisite checks should fail to detect a needed element, the installation should continue anyway.  Optional checks include operating system types and/or versions, presence of a compatible Java Run-time Environment (JRE), etc.  Note that non-optional (i.e. mandatory) prerequisite checks cannot be ignored by the silent install process.  These include such things as required installed programs, commands needed by the installer and/or the product itself (e.g. grep, cut, etc. for the installer and g++ for the compilers).  MAKE SURE YOUR LINUX DISTRO HAS INSTALLED DEVELOPMENT ENVIRONMENT, including gcc, g++, binutils, etc.  Many Linux distributions come as 'desktop' images and may not have all the gcc toolchain needed for developing applications by default.  Use your package manager to find and download all needed gcc and g++ toolchains.  Also, it is required to keep gcc and g++ at the same version - do not update one and not the other.  Keep them at the same version.

• PSET_INSTALL_DIR=/opt/intel/Compiler/11.1/038

This is the install directory where product content will be placed.  Permissions for the parent directories and file systems of this directory need to be enabled so that the user running the silent install could create them, but the directory itself does not need to exist prior to the installation.

• INSTALL_MODE=RPM

This directive tells the install program that the RPM method should be used to install the software.  This will only work if the install user is "root" or has full root priveleges and your distribution support RPM for package management.  In some cases, where the operating system of the target system does not support RPM or if the install program detects that the version of RPM supported by the operating system is flawed or otherwise incompatible with the install program, the installation will proceed but will switch to non-RPM mode automatically.  This is the case for certain legacy operating systems (e.g. SLES9) and for operating systems that provide an RPM utility, but do not use RPM to store or manage system-installed operating system infrastructure (e.g. Ubuntu, Debian).  THUS, Ubuntu and Debian users set this to INSTALL_MODE=NONRPM.

If the you do not want to use RPM, then this line should read "INSTALL_MODE=NONRPM".  In this case, the products will be installed to the same location, but instead of storing product information in the system's RPM database, the Intel product install information will be stored in a flat file called "intel_sdp_products.db", usually stored in /opt/intel (or in $HOME/intel for non-root users).

• ACCEPT_EULA=accept

This tells the install program that the invoking user has agreed to the EULA, or end user license agreement.  If this is not present in the INI file, the installation will not complete.

Note that silent install using this format does not currently support pre-selection of individual components.  In other words, if the desired installation is intended to include only some of the install components, but not all of them, the INI file here will not support this.  A custom INI created with the duplicate method will install all of the components available in a specific package.  If a custom install operation that only installs specific portions of the components is desired, it is suggested that the RPM install method be used for this.  (See below)

Silent Install Steps: "Copy and Repeat" Method of INI Creation

If you need to make the same sort of installation over and over again, one way to get the INI file right the first time is to run the installation program once interactively, using the options that meet the local needs, and record these options into an INI file that can be used to replicate this same install via silent install for future installations.

To do this, the user simply needs to add the "duplicate" option to the script invocation, and run a normal install, as follows:

prompt> ./install.sh --duplicate /tmp/my_install.ini

This "dash dash duplication" option will put the choices made by you into the file specified on the command line.  You can modify this recorded INI file as appropriate, then use it to perform additional or repeat installs.  The INI file created with this method may include a line "CONTINUE_WITH_INSTALLDIR_OVERWRITE" without the "=yes" on the end.  You will need to manually edit this INI file to add an "=yes" or "=no" to the end of this line, or else remove the CONTINUE_WITH_INSTALLDIR_OVERWRITE line altogether.  This limitation will be addressed in a future release.

Note that silent install using this format does not currently support pre-selection of individual components.  In other words, if the desired installation is intended to include only some of the install components, but not all of them, the INI file here will not support this.  A custom INI created with the duplicate method will install all of the components available in a specific package.  If a custom install operation that only installs specific portions of the components is desired, it is suggested that the RPM install method be used for this.  (See below)

RPM Command Line Installations

The files associated the Linux Compiler Professional products are stored in "RPM" files.  RPMs (short for Red Hat Package Manager).  They are grouped according to certain file type guidelines.  Each major product component will consist of one more or of these RPMs.  For non-RPM systems and for users who choose to install the product without using the RPM database of their target systems, an "underneath the hood" utility is embedded inside the installation program tools to extract the contents of the RPM files.

Changes for RPM in 11.1

Starting with the 11.1  packages, the Linux Compiler Professional packaging includes RPM files that also contain embedded installation functionality.  This means that key install behaviors such as environment script updating and symbolic link creation, which used to be only in the install program itself, are now embedded in the RPM files.  As a result, the experienced user can make use of the RPM files directly in order to install and remove Linux Compiler Professional 11.1 products.

Warning: this is truly for the experienced, Linux system savvy user.  Most RPM command capabilities require root privileges.  Improper use of rpm commands can corrupt and destroy a working system.

The changes done for the 11.1 Linux product are intended to ease the job of deploying the Linux Compiler Professional solution sets in enterprise deployments, including cluster environments. 

Product Layout for 11.1

The format of the install packages themselves was changed for 11.1.  Here is an example (for C++ package 11.1.038.

Top directory contents of l_cproc_p_11.1.038 package:

• cd_eject.sh - CD eject script used by install.sh
• install.sh - install script
• license.txt - end user license agreement
• pset - installation and licensing content directory
• Release_NotesC.pdf - product release notes
• rpm - directory containing all product content in RPM file format, plus the EULA and LPGL license

This is the RPM directory (l_cproc_p_11.1.038/rpm) layout for the 11.1 beta C/C++ product (IA-32 example):

• clicense - product EULA
• lgpltext - LGPL Eula
• intel-cproc038-11.1-1.i486.rpm - architecture-specific (IA-32) C/C++ compiler content
• intel-cprocsdk038-11.1-1.noarch.rpm - architecture-neutral core C/C++ compiler content
• intel-cproidb038-11.1-1.i486.rpm - architecture-specific (IA-32) debugger run-time files
• intel-cproidbsdk038-11.1-1.noarch.rpm - architecture-neutral debugger content
• intel-cproipp038-11.1-1.noarch.rpm - architecture-neutral IPP content
• intel-cproipplib038-11.1-1.i486.rpm - architecture-specific (IA-32) IPP run-time libraries
• intel-cproipplibdev038-11.1-1.i486.rpm - arch-specific (IA-32) IPP development libraries
• intel-cprolib038-11.1-1.i486.rpm - architecture-specific (IA-32) C/C++ run-time libraries
• intel-cprolibdev038-11.1-1.i486.rpm - architecture-specific (IA-32) C/C++ devel libraries
• intel-cpromkl038-11.1-1.noarch.rpm - architecture-neutral MKL content
• intel-cpromklib038-11.1-1.i486.rpm - architecture-specific (IA-32) run-time libraries
• intel-cpromklibdev038-11.1-1.i486.rpm - architecture-specific (IA-32) devel libraries
• intel-cprotbblib038-11.1-1.noarch.rpm - architecture-neutral TBB run-time libraries
• intel-cprotbblibdev038-11.1-1.noarch.rpm - archtecture-neutral TBB devel libraries and content

  (Note: TBB is special case "one RPM fits all" packaging)

This is the RPM directory layout for the 11.1 beta Fortran product (IA-32 example):

• flicense - product EULA
• intel-cprof038-11.1-1.i486.rpm - architecture-specific (IA-32) Fortran compiler content
• intel-cproflib038-11.1-1.i486.rpm - architecture-specific (IA-32) Fortran run-time libraries
• intel-cprofsdk038-11.1-1.noarch.rpm - architecture-neutral Fortran compiler content
• intel-cproidb038-11.1-1.i486.rpm - architecture-specific (IA-32) debugger content
• intel-cproidbsdk038-11.1-1.noarch.rpm - architecture-neutral debugger content
• intel-cprolib038-11.1-1.i486.rpm - architecture-specific (IA-32) C/C++ run-time library content
  (required for Fortran - same as the file included in the above C/C++ package)
• intel-cprolibdev038-11.1-1.i486.rpm - architecture-specific (IA-32) C/C++ devel library content
  (required for Fortran - same as the file included in the above C/C++ package)
• intel-cpromkl038-11.1-1.noarch.rpm - architecture-neutral MKL content
• intel-cpromklib038-11.1-1.i486.rpm - architecture-specific (IA-32) MKL run-time libraries
• intel-cpromklibdev038-11.1-1.i486.rpm - architecture-specific (IA-32) MKL devel libraries

Installing Compilers With the RPM Command Line

To install an 11.1 Linux Compiler Professional solution set via RPM command line, you should first ensure that a working license file or other licensing method (such as floating or network-served licenses) is already in place.  There is no license checking performed during RPM installation.  However, if you install without a license file you will get an 'cannot check out license' error when you try to use the compiler.

You are assumed to have complied with the End User License Agreement if you are performing an RPM command line installation.  The EULA is present in the parent installation tarball, and again duplicated inside the 'rpm' directory.  Please read this license agreement.  It is assumed you agree to this license agreement if you proceed with an rpm installation.

Once a license file or license method is in place, the user can install the products directly with these simple steps:

• Login as root or 'su' to root
• 'cd' to the package/rpm directory ( e.g. /tmp/l_cproc_p_11.1.038/rpm )
• Run the install command

prompt> rpm -i *.rpm

This completes without error in most cases.  If some system-level prerequisites, for required system libraries for example, are not met by the target operating system, a dependency warning may be returned by the rpm install.  There are no embedded detailed dependency checks inside the RPM install capabilities for required commands such as g++ or for optional requirements such as a valid supported operating system or supported JRE.  The embedded requirements are kept simple to ease installation for the general case, with two primary exceptions.  The first is requirement for a /usr/lib/libstdc++.so.5 to exist on the target system, and must match in 64bit or 32bit (there will be 2 copies of this library, one 64bit and one 32bit in 2 separate /lib paths, if you wish to be able to compile in 64bits and 32bits).  If libstdc++.so.5 is not available for your distribution but libstdc++.so.6 is, make libstdc++.so.5 a symbolic link to the .6 version. 

The second requirement is that the target operating system have at least the 3.0 version of "lsb" component installed.  Availability of this LSB component will, in the vast majority of cases, also ensure that other necessary system level libraries are available.  See LSB Support below for more information on getting the 'lsb' capability onto a target system.

If you believe that you have effectively installed the correct requirements on the target system and the dependency failures still persist, there is a fallback option, the "--nodeps" (dash dash nodeps) rpm switch.  Invoking 'rpm -i' with the --nodeps option will allow the rpm installation to succeed in most cases.

prompt> rpm -i --nodeps *.rpm

Again, this will get you past the perceived dependency issues, which may be unique to a particular distribution of Linux and not really a problem for the resulting installation.  But there is no assurance of complete success other than testing the resulting installation.

Other Special RPM Install Cases

If you are installing RPMs using the rpm command line, but using a multi-architecture package (such as the "combo" IA-32 / Intel64 package or a DVD package), you may want to install all of the RPMs that match their specific target machine's architecture.  Or, if you are installing onto an Intel64 system and want to include both the IA-32 and Intel64 components, you may want both of these included.  Here are some example rpm command line invocations:

prompt> rpm -i *.noarch.rpm *.i486.rpm

(installs all components needed for operation of IA-32 products)

prompt> rpm -i *.noarch.rpm *.i486.rpm *.x86_64.rpm

(installs all components needed for operation of IA-32 and Intel64 products)

prompt> rpm -i *.noarch.rpm *.ia64.rpm

(installs all components needed for operation of IA-64 products)

Certain Linux distributions do not like the idea of two RPM files having the same base name.  For example, the rpm versions of certain distros might complain that there is more than one instance of  intel-cproc023-11.1-1 on the command line when installing both the IA-32 and Intel64 RPMs onto the same machine.  For these distros, use the "--allmatches" ( dash dash allmatches ) command line switch:

prompt> rpm -i --allmatches *.noarch.rpm *.i486.rpm *.x86_64.rpm

Optionally, you may need to use the --force ( dash dash force ) switch in some cases.

Customizing the RPM Command Line

The rpm command has a long list of available options, including hooks to install from FTP and HTTP RPM repositories, features to examine contents of installed RPM-based programs and uninstalled RPM package files, etc.  Most of these are beyond the scope of this document.  See the Links section for references to external documentation on RPM.  Here are a couple of additional RPM switches, however, which may be routinely useful.

prompt> rpm -i --prefix /opt/intel/Compiler/11.1/035TEST *.rpm

( tells rpm to use /opt/intel/Compiler/11.1/023TEST as the target install directory)

prompt> rpm -i --replacefiles *.rpm

( tells rpm to replace any existing files on the system using the new RPM files)

prompt> rpm -i --replacepkgs *.rpm

( tells rpm to replace any existing package on the system using the new RPM files, even if they are already installed ... this may be useful in test applications where newer versions of a package with the same name are being tested )

Uninstallation Using RPM

Since the installation of Linux Compiler Professional 11.1 packages includes in its deliver all of the uninstall scripts, the easiest way to perform a product uninstall is to simply run the uninstall script that is created by the install process.  If you have a need to automate rpm-based uninstalls, however, a couple of "tricks" can be employed to make this simpler.  These should be used with caution, as with any system command performed from a privileged account.

Here is an example command line that will remove all RPM packages from a Linux Compiler Professional 11.1 package number "038":

prompt> rpm -e --allmatches `rpm -qa | grep intel-cpro | grep 038 | grep 11-1`

Note use of back-quotes.

Some Linux distributions will also complain about "multiple matches" during the uninstall process.  In this case, the "--allmatches" switch mentioned above can also be employed here.

A Short Word on Updates

The rpm structure and command set support the application of updates or "patches" to existing installations.  For example a util-1.1-2.rpm package may be issued that adds fixed content to some pre-existing util-1.1-1.rpm.   The existing release process for Linux Compiler Professional includes support for "version co-existence" or multiple installs of separate product versions.  So each new iteration of the product is unique from the previous version.  This means that Compiler Professional 11.1 packages are not available in "patch" form.  All product releases are stand-alone versions.  So use of the 'rpm -U' upgrade capability is not supported by our product delivery model at this time. 

LSB Support

LSB, or Linux Standard Base, is an effort sponsored by the Linux Foundation (http://www.linuxfoundation.org) to improve the interoperability of Linux operating systems and application software.  Intel is a major participant in Linux Foundation activities and has embraced LSB as a viable means of improving our products and our customers' use of those products.  To that end, we have included establishing LSB compliance as a part of our goals for our products and software packages in the future.

For the purposes of the Linux Compiler Professional 11.1 release, our primary objective is to product packages that adhere to LSB packaging requirements.  Most of the RPM changes mentioned above were done for this purpose.  To be specific, however, we should draw a distinction between product compliance and package compliance.  Because our compiler products must support a vast array of legacy constructs, the applications themselves may or may not be "certifiable" within the LSB guidelines, but our packages, i.e. our RPMs and install programs should be.  This is the primary reason for inclusion of the "lsb >= 3.0" embedded requirements being added to our RPMs.

Some of these Linux distributions come with LSB support already included in the operating system by default (e.g. SLES11).  For others, an external or optional package must be installed.  If supporting an environment that is using RPM command line installation and want to enable that site / system / systems to be able to install without using the dreaded "--nodeps" option, the best best is to acquire and install the companion LSB solution for that operating system.

The Linux Foundation website contains links to download resources for LSB, as to many of the vendor-specific support sites.  Check out these sites for information on adding LSB support to an existing operating system.

For RPM-based systems, a user can check on the status of LSB for their system, using a command like this:

prompt> rpm -q --provides lsb

This will tell if an 'lsb' RPM package is already installed and, if so, what version.

For our non-RPM supported operating systems, Ubuntu and Debian, the privileged user can use the Debian 'apt-get' facility to easily install the latest version of LSB supported by the specific distribution:

prompt> apt-get install lsb

Redistribution Package Installations

Redistribution packages allow applicaitons built with the Intel compilers to be run on client systems that do not have the Intel compilers installed (i.e. end-user systems).  These are ONLY needed on systems without the Intel compilers installed. A redistribution package has all the Intel dynamic libraries possibly needed for a dynamically linked application.  Alternatively, you can explore to -static-intel compiler switch to statically link all required Intel libraries into an application.  Redistribution packages were officially supported with the 11.0 release.  These will again be supported for the 11.1 release.

Installation is simple.  Once you extract the contents of the downloaded tarball (or accessing the redist contents of a DVD/image directory or media), you should simply invoke the "install.sh" script provided.  The user is instructed to accept a EULA, but there is no run-time license enforcement or any other software licensing included in the redist packages.  An uninstall script is produced during the redist install process, which provided for removal of the contents.

A note of caution: if the redist packages are installed on top of an existing Compiler Professional 11.1 package of the same "iteration" (e.g. 11.1.038), it will land on and replace existing files in that compiler installation by default.  Similarly, if the redist uninstall operation is run and the redist and compiler packages are sharing the same directory space, removing the redist package will break the compiler installation.  Since the redist packages are not intended for use by compiler users on their development machines, this should not be an issue in most environments.  But it is mentioned here in case situations come up where this might explain problems that have occurred.

Uninstall Instructions

As mentioned above, a standard uninstall script is included with each product installation, regardless of whether the install was performed using menu installs, RPM command line installs, or "silent" installs.  In all cases, using the provided uninstall script should work and is the usual preferred method of removing installed product..  There is one uninstall feature, however, that is undocumented and can be used to make life a little easier.  Here's an example invocation of that feature:

prompt> /opt/intel/Compiler/11.1/038/bin/ia32/uninstall_cproc.sh --default

This "--default" ( dash dash default ) option tells the uninstall script to use the "remove all" option and remove any Compiler Professional components associated with the specific package (in this case all 11.1.023 components, including C/C++, Fortran, IDB, MKL, TBB, and IPP, if installed).  There is no uninstall program interaction when this switch is used.

Links of Interest

The following links are provided for reference information.

• Maximum RPM - http://www.rpm.org/max-rpm/

Excellent on-line resource for understanding RPMs and their usage.

• Linux Foundation - http://www.linuxfoundation.org

Industry organization supporting standardization of Linux operating systems and applications.

• Linux LSB for Fedora - https://admin.fedoraproject.org/pkgdb/packages/name/redhat-lsb
• Linux LSB for RHEL5 (update notice) - https://rhn.redhat.com/errata/RHBA-2007-0590.html
• Linux LSB Info for Ubuntu - http://packages.ubuntu.com/search?keywords=lsb

The Intel Fortran compiler supports many features that are new to the latest revision of the Fortran standard, Fortran 2003 (ISO/IEC 1539:2004 ). Additional Fortran 2003 features will appear in future versions. Fortran 2003 features supported by the version 11.1 compiler include:

• The Fortran character set has been extended to contain the 8-bit ASCII characters ~ [ ] ` ^ { } | # @
• Names of length up to 63 characters
• Statements of up to 256 lines
• Square brackets [ ] are permitted to delimit array constructors instead of (/ /)
• Structure constructors with component names and default initialization
• Array constructors with type and character length specifications
• A named PARAMETER constant may be part of a complex constant
• Enumerators
• Allocatable components of derived types
• Allocatable scalar variables
• Deferred-length character entities
• PUBLIC types with PRIVATE components and PRIVATE types with PUBLIC components
• ERRMSG keyword for ALLOCATE and DEALLOCATE
• SOURCE= keyword for ALLOCATE
• Type extension
• CLASS declaration
• Polymorphic entities
• Inheritance association
• Deferred bindings and abstract types
• Type-bound procedures
• TYPE CONTAINS declaration
• ABSTRACT attribute
• DEFERRED attribute
• NON_OVERRIDABLE attribute
• ASYNCHRONOUS attribute and statement
• BIND(C) attribute and statement
• PROTECTED attribute and statement
• VALUE attribute and statement
• VOLATILE attribute and statement
• INTENT attribute for pointer objects
• Reallocation of allocatable variables on the left hand side of an assignment statement when the right hand side differs in shape or length (requires option "assume realloc_lhs")
• ASSOCIATE construct
• SELECT TYPE construct
• In all I/O statements, the following numeric values can be of any kind: UNIT=, IOSTAT=
• NAMELIST I/O is permitted on an internal file
• Restrictions on entities in a NAMELIST group are relaxed
• FLUSH statement
• WAIT statement
• ACCESS='STREAM' keyword for OPEN
• ASYNCHRONOUS keyword for OPEN and data transfer statements
• ID keyword for INQUIRE and data transfer statements
• POS keyword for data transfer statements
• PENDING keyword for INQUIRE
• The following OPEN numeric values can be of any kind: RECL=
• The following READ and WRITE numeric values can be of any kind: REC=, SIZE=
• The following INQUIRE numeric values can be of any kind: NEXTREC=, NUMBER=, RECL=, SIZE=
• Recursive I/O is allowed in the case where the new I/O being started is internal I/O that does not modify any internal file other than its own
• IEEE Infinities and NaNs are displayed by formatted output as specified by Fortran 2003
• BLANK, DELIM, ENCODING, IOMSG, PAD, ROUND, SIGN, SIZE I/O keywords
• DC, DP, RD, RC, RN, RP, RU, RZ format edit descriptors
• In an I/O format, the comma after a P edit descriptor is optional when followed by a repeat specifier
• Rename of user-defined operators in USE
• INTRINSIC and NON_INTRINSIC keywords in USE
• IMPORT statement
• Allocatable dummy arguments
• Allocatable function results
• PROCEDURE declaration
• Procedure pointers
• ABSTRACT INTERFACE
• PASS and NOPASS attributes
• Execution of a STOP statement displays a warning if an IEEE floating point exception is signaling
• The COUNT_RATE argument to the SYSTEM_CLOCK intrinsic may be a REAL of any kind
• COMMAND_ARGUMENT_COUNT intrinsic
• GET_COMMAND intrinsic
• GET_COMMAND_ARGUMENT intrinsic
• GET_ENVIRONMENT_VARIABLE intrinsic
• IS_IOSTAT_ END intrinsic
• IS_IOSTAT_EOR intrinsic
• MAX/MIN/MAXVAL/MINVAL/MAXLOC/MINLOC intrinsics allow CHARACTER arguments
• MAXLOC or MINLOC of a zero-sized array returns zero (requires option "assume noold_maxminloc")
• MOVE_ALLOC intrinsic
• NEW_LINE intrinsic
• SELECTED_CHAR_KIND intrinsic
• The following intrinsics take an optional KIND= argument: ACHAR, COUNT, IACHAR, ICHAR, INDEX, LBOUND, LEN, LEN_TRIM, MAXLOC, MINLOC, SCAN, SHAPE, SIZE, UBOUND, VERIFY
• Type inquiry intrinsic functions
• ISO_C_BINDING intrinsic module
• IEEE_EXCEPTIONS, IEEE_ARITHMETIC and IEEE_FEATURES intrinsic modules
• ISO_FORTRAN_ENV intrinsic module

Please see the compiler release notes for an updated list.

The Intel Fortran compiler also supports some features from the draft Fortran 2008 standard. These include:

• Passing internal procedures as actual arguments
• A procedure pointer can point to an internal procedure
• In ALLOCATE, if source-object does not have a shape specified, the shape is taken from the SOURCE= argument

Intel Fortran also includes a number of extensions to Fortran 2003, as well as command-line options that allow you to override the default actions of the compiler.

In some cases, the default behavior of the Intel Fortran Compiler does not conform to Fortran 2003 semantics.  The following table lists the compiler options which are not enabled by default and which must be specified to obtain full Fortran 2003 semantics. Note that, in some cases, enabling these options may lower run-time performance.

For more information, please refer to the "Compiler Options" section of the Intel Fortran Compiler documentation.