Code Compilation on Sapelo2 - Revision history

Shtsai: Added header for column 1 and table caption

2026-05-11T15:59:17Z

Added header for column 1 and table caption

← Older revision		Revision as of 11:59, 11 May 2026
Line 33:		Line 33:
	=== Summary of main Fortran and C/C++ compilers installed ===		=== Summary of main Fortran and C/C++ compilers installed ===
	{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"		{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"
			\|+Table showing various compilers for a given language
	\|-		\|-
	! scope="col" \|		! scope="col" \|Language
	! scope="col" \| NVHPC		! scope="col" \| NVHPC
	! scope="col" \| Intel		! scope="col" \| Intel

Shtsai: /* Where should I compile my code? */

2026-05-06T16:05:14Z

Where should I compile my code?

← Older revision		Revision as of 12:05, 6 May 2026
Line 3:		Line 3:
	==Where should I compile my code?==		==Where should I compile my code?==

	====<span style="color:~~black~~"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session started with the interact command.</big></span>====		<!--
			====<span style="color:darkred"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session started with the interact command.</big></span>====
			-->

			Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session started with the <code>interact</code> command.

	Code compilation can be done in an interactive session. To start an interactive session, first login into Sapelo2 and from there issue the <code>'''[[Running Jobs on Sapelo2#How to open an interactive session\|interact]]'''</code> command		Code compilation can be done in an interactive session. To start an interactive session, first login into Sapelo2 and from there issue the <code>'''[[Running Jobs on Sapelo2#How to open an interactive session\|interact]]'''</code> command

Shtsai: /* Where should I compile my code? */

2026-05-06T16:03:17Z

Where should I compile my code?

← Older revision		Revision as of 12:03, 6 May 2026
Line 3:		Line 3:
	==Where should I compile my code?==		==Where should I compile my code?==

	====<span style="color:~~darkred~~"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session started with the interact command.</big></span>====		====<span style="color:black"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session started with the interact command.</big></span>====


Line 23:		Line 23:

	----		----

	==Compilers==		==Compilers==

Shtsai: /* Linking with libraries */

2025-07-31T17:32:47Z

Linking with libraries

← Older revision		Revision as of 13:32, 31 July 2025
Line 405:		Line 405:
	Some library packages are installed along with some compiler toolchains. Examples of these are OpenBLAS, MKL, FFTW, etc. Other libraries are installed as a separate module, for example, Boost and GSL.		Some library packages are installed along with some compiler toolchains. Examples of these are OpenBLAS, MKL, FFTW, etc. Other libraries are installed as a separate module, for example, Boost and GSL.

	If you want to compile a code that uses a library that is not included with compiler toolchain, you will have to load a library module that uses a[[Available Toolchains and Toolchain Compatibility \| compatible]] toolchain. For example, if you want to compile your code with GCC 11.3.0 (or with the foss/~~2022a~~ toolchain), and you need to use GSL, you can load the GSL/2.7-GCC-11.3.0 module.		If you want to compile a code that uses a library that is not included with compiler toolchain, you will have to load a library module that uses a[[Available Toolchains and Toolchain Compatibility \| compatible]] toolchain. For example, if you want to compile your code with GCC 12.3.0 (or with the foss/2023a toolchain), and you need to use GSL, you can load the GSL/2.7-GCC-12.3.0 module.

	Also note that when you load a module for a library or an application, the full path to its installation directory will be stored in an environment variable called '''EBROOT''NAME''''', where ''NAME'' is the name of the application or library. For example, when you load a GSL module, the directory where the GSL libraries are installed will be in an environment variable called EBROOTGSL.		Also note that when you load a module for a library or an application, the full path to its installation directory will be stored in an environment variable called '''EBROOT''NAME''''', where ''NAME'' is the name of the application or library. For example, when you load a GSL module, the directory where the GSL libraries are installed will be in an environment variable called EBROOTGSL.
Line 414:		Line 414:
	[shtsai@d2-13 ~]$ module list		[shtsai@d2-13 ~]$ module list
	No modules loaded		No modules loaded
	[shtsai@d2-13 ~]$ module load GCC/11.3.0		[shtsai@d2-13 ~]$ module load GCC/12.3.0
	[shtsai@d2-13 ~]$ echo $EBROOTGCC		[shtsai@d2-13 ~]$ echo $EBROOTGCC
	/apps/eb/GCCcore/11.3.0		/apps/eb/GCCcore/12.3.0
	[shtsai@d2-13 ~]$ echo $EBROOTGSL		[shtsai@d2-13 ~]$ echo $EBROOTGSL

	[shtsai@d2-13 ~]$ module load GSL/2.7-GCC-11.3.0		[shtsai@d2-13 ~]$ module load GSL/2.7-GCC-12.3.0
	[shtsai@d2-13 ~]$ echo $EBROOTGSL		[shtsai@d2-13 ~]$ echo $EBROOTGSL
	/apps/eb/GSL/2.7-GCC-11.3.0		/apps/eb/GSL/2.7-GCC-12.3.0
	[shtsai@d2-13 ~]$		[shtsai@d2-13 ~]$
	</pre>		</pre>
Line 435:		Line 435:
	<code> -L${EBROOTGSL}/lib -lgsl -lgslcblas </code>		<code> -L${EBROOTGSL}/lib -lgsl -lgslcblas </code>

	'''Example of program compilation that uses GCC 11.3.0 and GSL v. 2.7:'''		'''Example of program compilation that uses GCC 12.3.0 and GSL v. 2.7:'''

	<pre class="gcommand">		<pre class="gcommand">
	module load GSL/2.7-GCC-11.3.0		module load GSL/2.7-GCC-12.3.0

	gcc -O program.c -I${EBROOTGSL}/include -L${EBROOTGSL}/lib -lgsl -lgslcblas -Wl,-rpath=${EBROOTGSL}/lib		gcc -O program.c -I${EBROOTGSL}/include -L${EBROOTGSL}/lib -lgsl -lgslcblas -Wl,-rpath=${EBROOTGSL}/lib

Shtsai: /* Compiler Toolchains */

2025-07-31T17:31:25Z

Compiler Toolchains

← Older revision		Revision as of 13:31, 31 July 2025
Line 285:		Line 285:
	[shtsai@d2-13 ~]$ module list		[shtsai@d2-13 ~]$ module list
	No modules loaded		No modules loaded
	[shtsai@d2-13 ~]$ module load foss/~~2022a~~		[shtsai@d2-13 ~]$ module load foss/2023a
	[shtsai@d2-13 ~]$ module list		[shtsai@d2-13 ~]$ module list

	Currently Loaded Modules:		Currently Loaded Modules:
	1) GCCcore/11.3.0 5) ~~numactl~~/2.0.14-GCCcore-11.3.0 9) ~~hwloc~~/2.7.1-~~GCCcore~~-11.3.0 13) ~~libfabric~~/1.15.1-GCCcore-11.3.0 17) ~~OpenBLAS~~/0.~~3.20~~-~~GCC~~-11.3.0 21) ~~FFTW~~.~~MPI/3~~.3.~~10-~~gompi~~-2022a~~		1) GCCcore/12.3.0 7) libxml2/2.11.4-GCCcore-12.3.0 13) libfabric/1.18.0-GCCcore-12.3.0 19) FFTW/3.3.10-GCC-12.3.0
	2) ~~zlib~~/1.2.12-GCCcore-11.3.0 6) XZ/5.2.5-GCCcore-11.3.0 10) ~~OpenSSL~~/1.~~1 14~~) ~~PMIx~~/4.1.2-~~GCCcore~~-11.3.0 18) ~~FlexiBLAS~~/3.2.0-GCC-11.3.0 22) ScaLAPACK/2.2.0-gompi-~~2022a~~-fb		2) zlib/1.2.13-GCCcore-12.3.0 8) libpciaccess/0.17-GCCcore-12.3.0 14) PMIx/4.2.4-GCCcore-12.3.0 20) gompi/2023a
	3) ~~binutils~~/2~~.38-GCCcore-11.3~~.0 ~~7) libxml2/2~~.~~9.13~~-GCCcore-11.3.0 11) libevent/2.1.12-GCCcore-11.3.0 15) ~~UCC~~/1.0~~.0-GCCcore-11~~.3.~~0 19) FFTW/3.3.10~~-GCC-11.3.0 23) foss/~~2022a~~		3) binutils/2.40-GCCcore-12.3.0 9) hwloc/2.9.1-GCCcore-12.3.0 15) UCC/1.2.0-GCCcore-12.3.0 21) FFTW.MPI/3.3.10-gompi-2023a
	4) ~~GCC~~/11.3.~~0 8) libpciaccess/0.16~~-GCCcore-11.3.0 12) UCX/1.12.1-GCCcore-11.3.0 16) ~~OpenMPI~~/4.1.4-GCC-11.3.0 ~~20) gompi/2022a~~		4) GCC/12.3.0 10) OpenSSL/1.1 16) OpenMPI/4.1.5-GCC-12.3.0 22) ScaLAPACK/2.2.0-gompi-2023a-fb
			5) numactl/2.0.16-GCCcore-12.3.0 11) libevent/2.1.12-GCCcore-12.3.0 17) OpenBLAS/0.3.23-GCC-12.3.0 23) foss/2023a
			6) XZ/5.4.2-GCCcore-12.3.0 12) UCX/1.14.1-GCCcore-12.3.0 18) FlexiBLAS/3.3.1-GCC-12.3.0

	</pre>		</pre>

Line 311:		Line 314:
	[shtsai@d2-13 ~]$ module list		[shtsai@d2-13 ~]$ module list
	No modules loaded		No modules loaded
	[shtsai@d2-13 ~]$ module load intel/~~2022a~~		[shtsai@d2-13 ~]$ module load intel/2023a
	[shtsai@d2-13 ~]$ module list		[shtsai@d2-13 ~]$ module list

	Currently Loaded Modules:		Currently Loaded Modules:
	1) GCCcore/11.3.0 3) ~~binutils/2.38~~-~~GCCcore-11.3.0 5) numactl~~/2.~~0.14-GCCcore-11.3~~.0 7) impi/2021.6.0-intel-compilers-~~2022~~.1.0 9) iimpi~~/2022a 11) intel/2022a~~		1) GCCcore/12.3.0 4) intel-compilers/2023.1.0 7) impi/2021.9.0-intel-compilers-2023.1.0 10) imkl-FFTW/2023.1.0-iimpi-2023a
	2) zlib/1.2.12-GCCcore-11.3.0 4) ~~intel-compilers~~/~~2022.1~~.0 ~~6) UCX/1~~.~~12.1~~-GCCcore-11.3.0 8) imkl/~~2022~~.1.0 10) ~~imkl~~-~~FFTW~~/~~2022~~.1.0-iimpi~~-2022a~~		2) zlib/1.2.13-GCCcore-12.3.0 5) numactl/2.0.16-GCCcore-12.3.0 8) imkl/2023.1.0 11) intel/2023a
			3) binutils/2.40-GCCcore-12.3.0 6) UCX/1.14.1-GCCcore-12.3.0 9) iimpi/2023a

	</pre>		</pre>

Shtsai at 17:28, 31 July 2025

2025-07-31T17:28:09Z

← Older revision		Revision as of 13:28, 31 July 2025
Line 31:		Line 31:
	\|-		\|-
	! scope="col" \|		! scope="col" \|
	! scope="col" \| ~~Portland Group (PGI)~~		! scope="col" \| NVHPC
	! scope="col" \| Intel		! scope="col" \| Intel
	! scope="col" \| GNU		! scope="col" \| GNU
Line 38:		Line 38:
	\|-		\|-

	\| Fortran77 \|\| ~~pgfortran~~		\| Fortran77 \|\| nvfortran
	\| ifort \|\| gfortran		\| ifort \|\| gfortran
	\| mpif77\|\| .f		\| mpif77\|\| .f
	\|-		\|-
	\| Fortran90 \|\| ~~pgfortran~~		\| Fortran90 \|\| nvfortran
	\| ifort \|\| gfortran\|\| mpif90\|\| .f90		\| ifort \|\| gfortran\|\| mpif90\|\| .f90
	\|-		\|-
	\| Fortran95 \|\| ~~pgfortran~~		\| Fortran95 \|\| nvfortran
	\| ifort \|\| gfortran \|\| mpifort \|\| .f95		\| ifort \|\| gfortran \|\| mpifort \|\| .f95
	\|-		\|-
	\|Fortran2003		\|Fortran2003
	\|~~pgfortran~~		\|nvfortran
	\|ifort		\|ifort
	\|gfortran		\|gfortran
Line 55:		Line 55:
	\|.f		\|.f
	\|-		\|-
	\| C \|\| ~~pgcc~~ \|\| icc \|\| gcc \|\| mpicc \|\| .c		\| C \|\| nvc \|\| icc \|\| gcc \|\| mpicc \|\| .c
	\|-		\|-
	\| C++ \|\| ~~pgc++~~ \|\| icpc \|\| g++ \|\| mpicxx \|\| .C, .cpp, .cc		\| C++ \|\| nvcc \|\| icpc \|\| g++ \|\| mpicxx \|\| .C, .cpp, .cc
	\|-		\|-

Line 80:		Line 80:

	Versions:		Versions:
	~~GCC/8.3.0~~
	~~GCC/10.2.0~~
	GCC/11.2.0		GCC/11.2.0
	GCC/11.3.0		GCC/11.3.0
	GCC/12.2.0		GCC/12.3.0
			GCC/13.2.0
			GCC/13.3.0
	Other possible modules matches:		Other possible modules matches:
	GCCcore		GCCcore
Line 92:		Line 92:
	This output indicates that the following versions of GCC compilers are available:		This output indicates that the following versions of GCC compilers are available:

	*Version 8.3.0, with binutils 2.32, provided by the GCC/8.3.0 module, includes C, C++, and Fortran compilers.
	*Version 10.2.0, with binutils 2.35, provided by the GCC/10.2.0 module, includes C, C++, and Fortran compilers.
	*Version 11.2.0, with binutils 2.37, provided by the GCC/11.2.0 module, includes C, C++, and Fortran compilers.		*Version 11.2.0, with binutils 2.37, provided by the GCC/11.2.0 module, includes C, C++, and Fortran compilers.
	*Version 11.3.0, with binutils 2.38, provided by the GCC/11.3.0 module, includes C, C++, and Fortran compilers.		*Version 11.3.0, with binutils 2.38, provided by the GCC/11.3.0 module, includes C, C++, and Fortran compilers.
	*Version 12.2.0, with binutils 2.39, provided by the GCC/12.2.0 module, includes C, C++, and Fortran compilers.		*Version 12.3.0, with binutils 2.40, provided by the GCC/12.3.0 module, includes C, C++, and Fortran compilers.
			*Version 13.2.0, with binutils 2.40, provided by the GCC/13.2.0 module, includes C, C++, and Fortran compilers.
			*Version 13.3.0, with binutils 2.42, provided by the GCC/13.3.0 module, includes C, C++, and Fortran compilers.


	We suggest that you run the<code> module spider GCC</code> command to check an updated list of GCC compilers available on the cluster.		We suggest that you run the<code> module spider GCC</code> command to check an updated list of GCC compilers available on the cluster.
Line 119:		Line 120:
	intel-compilers/2021.4.0		intel-compilers/2021.4.0
	intel-compilers/2022.1.0		intel-compilers/2022.1.0
	~~intel-compilers/2022.2.1~~
	intel-compilers/2023.1.0		intel-compilers/2023.1.0
			intel-compilers/2023.2.1
			intel-compilers/2024.2.0
	-----------------------------------------------------------------------------------------------------------------		-----------------------------------------------------------------------------------------------------------------
	</pre>		</pre>
Line 129:		Line 130:
	*Version 2021.4.0, provided by the intel-compilers/2021.4.0 module.		*Version 2021.4.0, provided by the intel-compilers/2021.4.0 module.
	*Version 2022.1.0, provided by the intel-compilers/2022.1.0 module.		*Version 2022.1.0, provided by the intel-compilers/2022.1.0 module.
	*Version 2022.2.1, provided by the intel-compilers/2022.2.1 module.
	*Version 2023.1.0, provided by the intel-compilers/2023.1.0 module.		*Version 2023.1.0, provided by the intel-compilers/2023.1.0 module.
	*Version ~~2019~~.5.~~281~~, provided by the ~~iccifort~~/~~2019~~.5.~~281~~ module		*Version 2023.2.1, provided by the intel-compilers/2023.2.1 module.
			*Version 2024.2.0, provided by the intel-compilers/2024.2.0 module.

	We suggest that you run the <code>module spider intel-compilers</code> or <code>module spider iccifort</code> command to check an updated list of Intel compilers available on the cluster.		We suggest that you run the <code>module spider intel-compilers</code> or <code>module spider iccifort</code> command to check an updated list of Intel compilers available on the cluster.
Line 152:		Line 153:

	Versions:		Versions:
	~~LLVM/12.0.1-GCCcore-11.2.0~~
	LLVM/14.0.3-GCCcore-11.3.0		LLVM/14.0.3-GCCcore-11.3.0
			LLVM/14.0.6-GCCcore-12.3.0-llvmlite
			LLVM/14.0.6-GCCcore-13.3.0-llvmlite
			LLVM/16.0.6-GCCcore-12.3.0
			LLVM/16.0.6-GCCcore-13.2.0
			LLVM/18.1.8-GCCcore-13.3.0-minimal

	-----------------------------------------------------------------------------------------------------------------------------------		-----------------------------------------------------------------------------------------------------------------------------------
	</pre>		</pre>
Line 159:		Line 165:
	=== How to load a compiler module ===		=== How to load a compiler module ===

	To use any of the compiler suite, please first load the corresponding module. For example, to use the GNU 11.3.0 compiler suite, load the module with<pre class="gcommand">		To use any of the compiler suite, please first load the corresponding module. For example, to use the GNU 12.3.0 compiler suite, load the module with<pre class="gcommand">
	module load GCC/11.3.0		module load GCC/12.3.0
	</pre>		</pre>
	Once this module is loaded the gcc, g++, and gfortran for GCC v. 11.3.0 will be available in your path.		Once this module is loaded the gcc, g++, and gfortran for GCC v. 12.3.0 will be available in your path.

	Please note that you can only have one compiler module loaded at a time.		Please note that you can only have one compiler module loaded at a time.

	=== Some commonly used compiler options ===		=== Some commonly used compiler options ===
			<!--
	==== PGI compiler suite (To be added on Sapelo2)====		==== PGI compiler suite (To be added on Sapelo2)====
	{\| class="wikitable unsortable" width="100%" border="1" cellspacing="0" cellpadding="2" align="center"		{\| class="wikitable unsortable" width="100%" border="1" cellspacing="0" cellpadding="2" align="center"
Line 202:		Line 208:
	'''NOTE'''		'''NOTE'''
	When using optimization options, please check if your code becomes more efficient (in some cases optimization options will slow the code down) and if it still generates correct results. Many other compiler options are available. For more information on the PGI compilers, you can view the manual pages with the commands '''man pgf90''', '''man pgcc''', etc, after loading the PGI module.		When using optimization options, please check if your code becomes more efficient (in some cases optimization options will slow the code down) and if it still generates correct results. Many other compiler options are available. For more information on the PGI compilers, you can view the manual pages with the commands '''man pgf90''', '''man pgcc''', etc, after loading the PGI module.
			-->
	====Intel compiler suite====		====Intel compiler suite====
	{\| class="wikitable unsortable" width="100%" border="1" cellspacing="0" cellpadding="2" align="center"		{\| class="wikitable unsortable" width="100%" border="1" cellspacing="0" cellpadding="2" align="center"

Moses at 17:23, 6 September 2023

2023-09-06T17:23:58Z

← Older revision		Revision as of 13:23, 6 September 2023
Line 3:		Line 3:
	==Where should I compile my code?==		==Where should I compile my code?==

	====<span style="color:darkred"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session ~~opened~~ with the interact command.</big></span>====		====<span style="color:darkred"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session started with the interact command.</big></span>====


	Code compilation can be done in an interactive session. To start an interactive session, first login into Sapelo2 and from there issue the <code>interact</code> command		Code compilation can be done in an interactive session. To start an interactive session, first login into Sapelo2 and from there issue the <code>'''[[Running Jobs on Sapelo2#How to open an interactive session\|interact]]'''</code> command
	<pre class="gcommand">		<pre class="gcommand">
	interact		interact

Moses at 17:19, 6 September 2023

2023-09-06T17:19:13Z

← Older revision		Revision as of 13:19, 6 September 2023
Line 3:		Line 3:
	==Where should I compile my code?==		==Where should I compile my code?==

	==== <span style="color:darkred"><big>IMPORTANT: Please do NOT compile code on the login node. Instead, ~~please first start~~ an interactive session ~~by using~~ interact command ~~and compile the code on the interactive node~~.</big></span> ====		====<span style="color:darkred"><big>IMPORTANT: Please DO NOT compile source code on the login node. Instead, compile your code in an interactive session opened with the interact command.</big></span>====

Moses at 17:11, 6 September 2023

2023-09-06T17:11:01Z

← Older revision		Revision as of 13:11, 6 September 2023
Line 3:		Line 3:
	==Where should I compile my code?==		==Where should I compile my code?==

	==== <span style="color:darkred"><big>IMPORTANT: Please do NOT compile code on the login node. Instead, please first start an interactive session ~~with~~ interact command and compile the code on the interactive node.</big></span> ====		==== <span style="color:darkred"><big>IMPORTANT: Please do NOT compile code on the login node. Instead, please first start an interactive session by using interact command and compile the code on the interactive node.</big></span> ====

Moses at 20:37, 5 September 2023

2023-09-05T20:37:47Z

← Older revision		Revision as of 16:37, 5 September 2023
Line 4:		Line 4:

	==== <span style="color:darkred"><big>IMPORTANT: Please do NOT compile code on the login node. Instead, please first start an interactive session with interact command and compile the code on the interactive node.</big></span> ====		==== <span style="color:darkred"><big>IMPORTANT: Please do NOT compile code on the login node. Instead, please first start an interactive session with interact command and compile the code on the interactive node.</big></span> ====


	Code compilation can be done in an interactive session. To start an interactive session, first login into Sapelo2 and from there issue the <code>interact</code> command		Code compilation can be done in an interactive session. To start an interactive session, first login into Sapelo2 and from there issue the <code>interact</code> command
	<pre class="gcommand">		<pre class="gcommand">
Line 166:		Line 168:
	=== Some commonly used compiler options ===		=== Some commonly used compiler options ===

	==== PGI compiler suite (to be added on Sapelo2)====		==== PGI compiler suite (To be added on Sapelo2)====
	{\| class="wikitable unsortable" width="100%" border="1" cellspacing="0" cellpadding="2" align="center"		{\| class="wikitable unsortable" width="100%" border="1" cellspacing="0" cellpadding="2" align="center"
	\|-		\|-