ifc. efc. ldb. ias. The following list has additional comments on the compiler package. See the Known Limitations section for additional information.
-O3 compiler option, better OpenMP* support and auto-parallelization
available with the -parallel compiler option. Due to changes
in the Fortran libraries, it is necessary to recompile object and library files
if upgrading from the 5.0 versions of the Intel Compilers. In addition, other files
the compiler generates should be re-created such as the work.pc, work.pcl,
PGO files (*.dyn, pgopti.dpi), etc, if upgrading from the 5.0 version.
POSIX threaded programs that require a large stack size may not run correctly on some versions of Linux because of hard-coded stack size limits in some versions of the Linux POSIX threads libraries. See the section [Known Limitations] for additional details.
Version 6.0 of the Intel compilers for Linux does not include
a cross compiler for Itanium-based applications. Native compilers,
that run on a computer with an Itanium processor, are available.
Direct object generation is now enabled in the compiler for Itanium-based applications,
that is, the compiler will directly generate object files without automatically
generating an intermediate assembly file and subsequently invoke the assembler.
Direct object generation may be disabled using use the compiler option,
-use_asm.
It is no longer necessary to run a script to create several new environment variables at the start of each session. The only required variables are PATH and LD_LIBRARY_PATH, which may be updated by the .login file. Refer to section see the Compiler Environment and configuration scripts section.
The Intel Compiler's help content is available from the man command
after setting up the compiler environment, see the
Compiler Environment and configuration scripts
section. Then, run man ifc or
man efc.
ifc.
ldb
efc.
The native compiler runs on a computer with an Itanium processor.
ldb.
ias.
The documentation is installed in the
<install-dir>/compiler60/docs directory. Also,
an HTML index document can be found at
<install-dir>/compiler60/docs/fcompindex.htm. For information on the GNU
glibc C language library, documentation can be obtained from the Linux
OS vendor or from the GNU web site, www.gnu.org.
Edit-->Preferences-->Advanced-->enable Java
Edit-->Preferences-->Advanced-->enable JavaScript
Edit-->Preferences-->Advanced-->enable stylesheets
xpdf
utility or install
acroread,
the Acrobat* Reader for Linux. It is recommended to view
the PDF documentation with Acrobat running within Netscape as this
provides additional navigation features.
To enable Netscape to start acroread, acroread needs to be installed in
a directory searched by your PATH environment variable and you need to
edit the browser's preferences. NOTE: If acroread isn't configured correctly,
you can overwrite the PDF files, requiring you to reinstall them.
If improperly configured, the acroread browser may prompt you
to Save-As file, which if you click OK can overwrite the PDF documentation files.
Perform these steps needed to update your preferences for acroread:
Edit --> Preferences --> Navigator --> Applications--> newAnother method to configure acroread is to add the following entry in the file .mailcap in your home directory:
Description: Portable Document Format
MIMEType: application/pdf
Suffixes: pdf
Application: acroread %s
application/pdf; acroread %sDepending on your version of the Netscape browser, you might need to disable (turn OFF) the "Automatically load images" option or the browser will freeze when you open the HTML documentation files, this means that you will then need to click on the images in the documentation if you want to see them while paging through the documentation with the browser. Turn OFF this option by clicking on: Edit-->Preferences-->Advanced-->Automatically load images and other data types.
install.
It's possible to install without root access
by unpacking the RPM files with rpm2cpio and editing the
compiler environment and configuration files, described below,
but this installation method is not supported.
-U --replacefiles,
are recommended to update existing
files. The recommended installation directory is
/opt/intel.
x to exit.
source <install-dir>/compiler60/ia32/bin/ifcvars.sh(.csh)
source <install-dir>/compiler60/ia64/bin/efcvars.sh(.csh)
To receive technical support and product updates for the tools provided in this product you need to register See Technical Support and Feedback for registration instructions.
<install-dir>/compiler60/ia32/bin/ifcvars.sh(.csh)
for IA-32 applications, and <install-dir>/compiler60/ia64/bin/efcvars.sh(.csh)
for Itanium processor-based applications.
The installation creates configuration files,
<install-dir>/compiler60/ia32/bin/ifc.cfg and
<install-dir>/compiler60/ia64/bin/efc.cfg.
They contain common settings and can be used to add additional default
options. Note, if you install a compiler update package, you need to
rename the config files to avoid being overwritten.
install
script prevent the compilers from working correctly when installed in different
directories. However, the compilers should still be untar-ed into separate
directories if you downloaded the electronic version.
There are certain libraries that are common between the Intel C++ Compilers and the Intel Fortan Compilers. When installing updates to either C++ or Fortran, we recommend that the other one be updated. Otherwise there may be a library mismatch causing unexpected behavior of the compiler(s) or the compiled code.
uninstall
script is provided to uninstall the compiler packages.
<install-dir>/compiler60/ia32/bin/uninstall
<install-dir>/compiler60/ia64/bin/uninstall
These limits also apply to OpenMP programs (-openmp) and automatically generated parallel programs (-parallel) with the Intel compilers, because the Intel compilers use the POSIX threads library to implement OpenMP based and automatically generated parallelism. Threaded programs that exceed the stack space limit usually experience segmentation violations or addressing errors.
To avoid these limitations, please use a version of glibc built with the "FLOATING_STACKS" parameter defined, typically version 2.2.4 or later for both IA-32 and Itanium Processor Family. Then use the ulimit -s .... command to set the maximum shell stack size to an explicit large value (units of KBytes) and also set the KMP_STACKSIZE environment variable to the needed thread stacksize in bytes. A shell stacksize limit of "unlimited" does not work - it causes a fixed hard limit to be imposed. Note : In the bash shell, ulimit -s can be used to set a large maximum stack size only once. In the C shell, limit -stacksize can be used to reset the maximum stacksize repeatedly.
This solution has been tested on glibc version 2.2.4-13 for IA-32 and glibc 2.2.4-19 for Itanium Processor Family as found in the RedHat 7.2 Linux distribution. For glibc 2.2.4-13 on IA-32, the shared version of the POSIX threads library must be used, (there should not be a -static flag in the compiler .cfg file or on the command line).
The Linux system libraries and the compiler libraries are not built with the -align option. Therefore, if you compile with the -align option and make a call to compiler distributed or system library, and have long long, double, or long double in your interface, you will get the wrong answer due to the difference in alignment. Any code built with -align cannot make calls to libraries that use these types in their interfaces unless they are built with -align (in which case they will not work without -align).
Please click on the appropriate link below to see additional notes and known limitations in the latest version of the compiler.
Please follow these guidelines when submitting your problem report or product suggestion:
icid.
When icid is executed,
the package ID is written to standard output. See the Installation section
for details on setting up the compiler environment.
install error for the issue type.
See Technical
Support and Feedback for instructions on how to register for support.
If you were not able to install the compiler or cannot run icid
to determine the package ID, enter the filename you downloaded as the package ID
and explain in the issue that you were not able to run icid.
A technical support engineer will respond within one (1) Intel business day.
Copyright (C) 2000, 2001, 2002 Intel Corporation. All Rights Reserved.