Difference between revisions of "Intel Compiler"
| Line 12: | Line 12: | ||
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de" | export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de" | ||
| − | intel_arch=intel64 | + | intel_arch="intel64" |
| − | if [ `uname -m` == "i686" ]; then | + | if [[ `uname -m` == "i686" ]]; then |
| − | intel_arch=" | + | intel_arch="ia32" |
fi | fi | ||
iccvars=/opt/intel/Compiler/11.0/069/bin/iccvars.sh | iccvars=/opt/intel/Compiler/11.0/069/bin/iccvars.sh | ||
if [ -f $iccvars ]; then | if [ -f $iccvars ]; then | ||
| − | . $iccvars intel_arch | + | . $iccvars $intel_arch |
fi | fi | ||
ifortvars=/opt/intel/Compiler/11.0/069/bin/iccvars.sh | ifortvars=/opt/intel/Compiler/11.0/069/bin/iccvars.sh | ||
if [ -f $ifortvars ]; then | if [ -f $ifortvars ]; then | ||
| − | . $ifortvars | + | . $ifortvars $intel_arch |
fi | fi | ||
</pre> | </pre> | ||
| − | == 32/64 Issues == | + | == 32/64 bit Issues == |
| − | If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine think can get more complicates. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and less important the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. | + | If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine think can get more complicates. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and less important the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment. |
| + | |||
| + | If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram. | ||
Revision as of 16:43, 5 December 2008
This page describes, how to setup your environment for using our temporary Intel Compiler Installtion. The instruction are for bash shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration.
We provide the recent version 11 of the Intel compiler suite for Fortran, C/C++ and the full set performance libraries like MKL, TBB, Cluster_OMP.
.bashrc
In order to use the installation you have to modify your .bashrc. Open the file with you favorite editor and append the following lines.
#Intel Compiler Setup
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"
intel_arch="intel64"
if [[ `uname -m` == "i686" ]]; then
intel_arch="ia32"
fi
iccvars=/opt/intel/Compiler/11.0/069/bin/iccvars.sh
if [ -f $iccvars ]; then
. $iccvars $intel_arch
fi
ifortvars=/opt/intel/Compiler/11.0/069/bin/iccvars.sh
if [ -f $ifortvars ]; then
. $ifortvars $intel_arch
fi
32/64 bit Issues
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine think can get more complicates. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and less important the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.
