Intel compilers - Revision history

imported>Huston: No more condor pool

2023-03-13T14:25:30Z

No more condor pool

← Older revision		Revision as of 14:25, 13 March 2023
Line 10:		Line 10:

	'''''NOTE:'''''		'''''NOTE:'''''
	If compiling code for use on [[Condor\|condor]], you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.		The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.


Line 26:		Line 26:
	'''You must compile your code using the proper compiler for the platform on which you will want to run your executable!		'''You must compile your code using the proper compiler for the platform on which you will want to run your executable!

	While the 32-bit compiler ''might'' compile code on a 64-bit machine, there's no guarantee that all the necessary 32-bit libraries will be available on all machines~~... especially if you intend to use condor~~. Stick with the 64-bit compiler and you'll save yourself a lot of headaches.		While the 32-bit compiler ''might'' compile code on a 64-bit machine, there's no guarantee that all the necessary 32-bit libraries will be available on all machines. Stick with the 64-bit compiler and you'll save yourself a lot of headaches.

	If you're not sure what platform you're using, run the following command:		If you're not sure what platform you're using, run the following command:

imported>Huston at 13:00, 15 October 2015

2015-10-15T13:00:00Z

← Older revision		Revision as of 13:00, 15 October 2015
Line 10:		Line 10:

	'''''NOTE:'''''		'''''NOTE:'''''
	If compiling code for use on ~~[[Cluster Computing\|Hydra]] or~~ [[Condor\|condor]], you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.		If compiling code for use on [[Condor\|condor]], you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.

imported>Huston: Use Modules

2011-10-31T19:38:57Z

Use Modules

@@ Line 3: / Line 3: @@
 == Setup ==
-There are multiple versions of the Intel compilers installed.  Depending on which version you want to run, you'll need to source some scripts to get all your paths setup properly.  Add one of these sets of lines to your shell startup file (.bashrc for bash users, .cshrc for tcsh users).
+There are multiple versions of the Intel compilers installed.  Depending on which version you want to run, you'll need to load the appropriate [[Modules|module]] with the command <tt>module load intel</tt>.  This sets up both the C and Fortran compilers for the appropriate architecture on which you're running the command; see the output of <tt>module help intel</tt> for information about cross-compiling.
 == Use ==
-The Intel compiler suite is installed in /usr/peyton/intel, consisting of the C (icc) and Fortran (ifort) compilers as well as a debugger from Intel.
+The Intel compiler suite consists of the C (icc) and Fortran (ifort) compilers.
 '''''NOTE:'''''

imported>Lkoven: Removed the warning about having to use older compilers on some machines; modified the note about -static to suggest it for both condor and hydra

2009-03-12T23:11:40Z

Removed the warning about having to use older compilers on some machines; modified the note about -static to suggest it for both condor and hydra

← Older revision		Revision as of 23:11, 12 March 2009
Line 41:		Line 41:

	'''''NOTE:'''''		'''''NOTE:'''''
	~~: The compilers may not run on all Linux machines in the building (should be at least RedHat 7.2). You will need to~~ use ~~compiler version 9 or below~~ on ~~machines running RedHat 7.x~~ or ~~below (I believe hydra is the last one). Also note that in the case of Hydra~~, you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.		If compiling code for use on [[Cluster Computing\|Hydra]] or [[Condor\|condor]], you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.

imported>Lkoven: Removed references to 8.1, 9.0; changed 10.0 to 10.1; added 11.0 information

2009-03-12T23:06:36Z

Removed references to 8.1, 9.0; changed 10.0 to 10.1; added 11.0 information

← Older revision		Revision as of 23:06, 12 March 2009
Line 4:		Line 4:
	== Setup ==		== Setup ==
	There are multiple versions of the Intel compilers installed. Depending on which version you want to run, you'll need to source some scripts to get all your paths setup properly. Add one of these sets of lines to your shell startup file (.bashrc for bash users, .cshrc for tcsh users).		There are multiple versions of the Intel compilers installed. Depending on which version you want to run, you'll need to source some scripts to get all your paths setup properly. Add one of these sets of lines to your shell startup file (.bashrc for bash users, .cshrc for tcsh users).
	* Version 8.1		* Version 11.0
	** bash		*: Starting with version 11.0, the Intel Compiler directory structure has changed a bit. The C++ compiler, Fortran compiler, and Intel Debugger are all within the same directory tree. The new method for calling the setup script is as follows (replace <arch> with one of ia32 for 32-bit machines, or intel64 for 64-bit machines):
	**: ~~<tt>source /usr/peyton/intel/8~~.~~1/icc/bin/iccvars~~.sh<~~/tt~~>		** bash
	**~~: <tt>source /usr/peyton/intel/8.1/ifc/bin/ifortvars.sh</tt>~~		*** C/C++ Compiler & Debugger
	**~~: <tt>source~~ /~~usr/peyton/intel/8.1/idb/bin/idbvars.sh</tt>~~		***: <tt>source /usr/peyton/intel/11.0/bin/iccvars.sh <arch></tt>
	** tcsh		*** Fortran Compiler & Debugger
	**: <tt>source /usr/peyton/intel/8.~~1/icc~~/bin/iccvars.~~csh</tt>~~		***: <tt>source /usr/peyton/intel/11.0/bin/ifortvars.sh <arch></tt>
	**: <tt>~~source /usr/peyton/intel/8.1/ifc/bin/ifortvars.csh~~</tt>		** csh/tcsh
	**~~: <tt>source /usr/peyton/intel/8.1/idb/bin/idbvars.csh</tt>~~		*** C/C++ Compiler & Debugger
	* ~~Version 9.0~~		***: <tt>source /usr/peyton/intel/11.0/bin/iccvars.csh <arch></tt>
	** bash		*** Fortran Compiler & Debugger
	**: <tt>source /usr/peyton/intel/9.0~~/cc~~/bin/~~iccvars~~.sh</tt>		***: <tt>source /usr/peyton/intel/11.0/bin/ifortvars.sch <arch></tt>
	**~~: <tt>source~~ /~~usr/peyton/intel/9.0/fc/bin/ifortvars.sh</tt>~~
	**~~: <tt>source /usr/peyton/intel~~/~~9.0/idb/bin/idbvars.sh</tt>~~		* Version 10.1
	** tcsh
	**: <tt>source /usr/peyton/intel/9.0~~/cc~~/bin/iccvars.csh</tt>
	**: <tt>source /usr/peyton/intel/9.0~~/fc~~/bin/ifortvars.~~csh~~<~~/tt~~>
	**: <tt>source /usr/peyton/intel/9.0/idb/bin/idbvars.csh</tt>
	* Version 10.0
	*: Starting with version 10.0, we have both 32-bit and 64-bit versions of the Intel compiler installed. See the [[#32 vs. 64-bit\|important notes]] below.
	** 32-bit		** 32-bit
	*** bash		*** bash
	***: <tt>source /usr/peyton/intel/10.0/cc/bin/iccvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.1/cc32/bin/iccvars.sh</tt>
	***: <tt>source /usr/peyton/intel/10.0/fc/bin/ifortvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.1/fc32/bin/ifortvars.sh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~idb~~/bin/idbvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.1/idb32/bin/idbvars.sh</tt>
	*** tcsh		*** tcsh
	***: <tt>source /usr/peyton/intel/10.0/cc/bin/iccvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.1/cc32/bin/iccvars.csh</tt>
	***: <tt>source /usr/peyton/intel/10.0/fc/bin/ifortvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.1/fc32/bin/ifortvars.csh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~idb~~/bin/idbvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.1/idb32/bin/idbvars.csh</tt>
	** 64-bit		** 64-bit
	*** bash		*** bash
	***: <tt>source /usr/peyton/intel/10.0/~~cce~~/bin/iccvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.1/cc64/bin/iccvars.sh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~fce~~/bin/ifortvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.1/fc64/bin/ifortvars.sh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~idbe~~/bin/idbvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.1/idb64/bin/idbvars.sh</tt>
	*** tcsh		*** tcsh
	***: <tt>source /usr/peyton/intel/10.0/~~cce~~/bin/iccvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.1/cc64/bin/iccvars.csh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~fce~~/bin/ifortvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.1/fc64/bin/ifortvars.csh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~idbe~~/bin/idbvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.1/idb64/bin/idbvars.csh</tt>

	== Use ==		== Use ==

imported>Lkoven: /* Setup */

2008-07-20T03:54:06Z

Setup

← Older revision		Revision as of 03:54, 20 July 2008
Line 39:		Line 39:
	***: <tt>source /usr/peyton/intel/10.0/idbe/bin/idbvars.sh</tt>		***: <tt>source /usr/peyton/intel/10.0/idbe/bin/idbvars.sh</tt>
	*** tcsh		*** tcsh
	***: <tt>source /usr/peyton/intel/10.0/cc/bin/iccvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.0/cce/bin/iccvars.csh</tt>
	***: <tt>source /usr/peyton/intel/10.0/fc/bin/ifortvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.0/fce/bin/ifortvars.csh</tt>
	***: <tt>source /usr/peyton/intel/10.0/~~idb~~/bin/idbvars.csh</tt>		***: <tt>source /usr/peyton/intel/10.0/idbe/bin/idbvars.csh</tt>

	== Use ==		== Use ==

imported>Lkoven: /* Use */ Added a note that 10 won't work on distros older than RH8, added a comment about how to find out what bitness your machine has

2007-09-27T16:40:49Z

Use: Added a note that 10 won't work on distros older than RH8, added a comment about how to find out what bitness your machine has

← Older revision		Revision as of 16:40, 27 September 2007
Line 47:		Line 47:

	'''''NOTE:'''''		'''''NOTE:'''''
	: The compilers may not run on all Linux machines in the building (should be at least RedHat 7.2). Also note that in the case of Hydra, you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.		: The compilers may not run on all Linux machines in the building (should be at least RedHat 7.2). You will need to use compiler version 9 or below on machines running RedHat 7.x or below (I believe hydra is the last one). Also note that in the case of Hydra, you should probably build statically linked binaries to ensure the libraries needed to execute the program are available on the compute nodes (linker option '-static'). The license we have for the compilers allows for 2 users to compile code simultaneously; if you get an error about compiling, try waiting a few minutes and running the command again.


Line 64:		Line 64:

	While the 32-bit compiler ''might'' compile code on a 64-bit machine, there's no guarantee that all the necessary 32-bit libraries will be available on all machines... especially if you intend to use condor. Stick with the 64-bit compiler and you'll save yourself a lot of headaches.		While the 32-bit compiler ''might'' compile code on a 64-bit machine, there's no guarantee that all the necessary 32-bit libraries will be available on all machines... especially if you intend to use condor. Stick with the 64-bit compiler and you'll save yourself a lot of headaches.

			If you're not sure what platform you're using, run the following command:

			<tt>uname -i</tt>

			Anything in the form of ix86 is 32-bit, x86_64 is 64-bit

	[[Category:Software]]		[[Category:Software]]

imported>Lkoven at 16:29, 27 September 2007

2007-09-27T16:29:57Z

← Older revision		Revision as of 16:29, 27 September 2007
Line 1:		Line 1:
	~~{{inuse\|1 hour to add information about the Intel 10.0 compiler}}~~
	Many have found that the compilers from Intel generate faster code than the standard GNU compilers. We try to keep up with the licensing from Intel so we have somewhat recent versions of the compilers installed, and below you'll find more information about them.		Many have found that the compilers from Intel generate faster code than the standard GNU compilers. We try to keep up with the licensing from Intel so we have somewhat recent versions of the compilers installed, and below you'll find more information about them.

imported>Lkoven: Added information about the 10.0 compiler and some notes about 32 and 64 bit compiling

2007-09-27T16:29:01Z

Added information about the 10.0 compiler and some notes about 32 and 64 bit compiling

@@ Line 23: / Line 23: @@
 **: <tt>source /usr/peyton/intel/9.0/fc/bin/ifortvars.csh</tt>
 **: <tt>source /usr/peyton/intel/9.0/idb/bin/idbvars.csh</tt>
+* Version 10.0
 == Use ==
@@ Line 38: / Line 57: @@
 === Linking ===
 Some users have had to use the linker flag -Vaxlib, otherwise the compiler complained about iargc or get_arg functions.  Another issue related to the Intel compilers use on Fedora Core 2 machines is described on the page http://newweb.ices.utexas.edu/misc/ctype.c.  This may no longer be an issue, as I think the compiler version that was installed has since been upgraded.
 [[Category:Software]]

imported>Lkoven at 15:47, 27 September 2007

2007-09-27T15:47:12Z

← Older revision		Revision as of 15:47, 27 September 2007
Line 1:		Line 1:
			{{inuse\|1 hour to add information about the Intel 10.0 compiler}}
	Many have found that the compilers from Intel generate faster code than the standard GNU compilers. We try to keep up with the licensing from Intel so we have somewhat recent versions of the compilers installed, and below you'll find more information about them.		Many have found that the compilers from Intel generate faster code than the standard GNU compilers. We try to keep up with the licensing from Intel so we have somewhat recent versions of the compilers installed, and below you'll find more information about them.