Compilers:Intel: Difference between revisions
Nic-systems (talk | contribs) mNo edit summary |
Nic-systems (talk | contribs) mNo edit summary |
||
| Line 19: | Line 19: | ||
</pre> | </pre> | ||
== Testing == | |||
Here's an easy way to make sure the compiler works: | |||
<pre> | |||
cat <<EOF > hello-test.cpp | |||
#include <iostream> | |||
using namespace std; | |||
int main(int argc, char **argv) | |||
{ | |||
cout <<"Hello"<<endl; | |||
return 0; | |||
} | |||
EOF | |||
source /opt/intel/cce/9.0/bin/iccvars.sh | |||
icpc hello-test.cpp -o hello | |||
</pre> | |||
[[Category:Compilers]] | [[Category:Compilers]] | ||
Latest revision as of 00:23, 27 September 2006
Intel offers compilers that will generate binaries that are better tuned for their target archtecture than those generated by the Gnu compilers.
Download
http://www.intel.com/cd/software/products/asmo-na/eng/compilers/284132.htm
Licensing
We use the free non-commercial licenses offered on Intel's website. If a host already has the compilers installed, check /opt/intel/licenses/ for the license files. They do not seem to be tied to a particular version, and do not expire. If you don't see a license, just request a new one.
Installing
The installation process is pretty well documented by Intel inside <package-dir>/INSTALL.txt. I usually install the complete package. I also had some issue entering the license number in the installer by hand, the only thing I could get to work was copying the .lic files to a temporary location on the filesystem and then pointing the installer to their path.
wget http://registrationcenter.cps.intel.com/irc_nas/69/l_cc_c_9.0.032.tar.gz tar -zxvf l_cc_c_9.0.032.tar.gz cd l_cc_c_9.0.032 less INSTALL.txt ./install.sh
Testing
Here's an easy way to make sure the compiler works:
cat <<EOF > hello-test.cpp
#include <iostream>
using namespace std;
int main(int argc, char **argv)
{
cout <<"Hello"<<endl;
return 0;
}
EOF
source /opt/intel/cce/9.0/bin/iccvars.sh
icpc hello-test.cpp -o hello