Software Setup¶
This episode describes how to compile and run the CUDA exercises. To follow the exercises you need a machine with an NVIDIA GPU — either your own workstation or a node of a cluster — with the CUDA Toolkit (nvcc) or, for CUDA Fortran, the NVIDIA HPC SDK (nvfortran) installed. The episode shows the compiler commands for both languages, the flags for optimisation, debugging and profiling, and how to link CUDA libraries. Connecting to a specific cluster — logging in, loading modules, and submitting GPU jobs — depends on the system you use and is covered separately by the material your training provider supplies for that system.
Objectives
Know how to compile CUDA C/C++ and CUDA Fortran programs
Know which compiler flags to use for optimisation, debugging, and profiling
Instructor note
10 min teaching
Compiling CUDA programs¶
$ nvcc -o program program.cu
$ nvcc -O3 -o program program.cu # optimise host code (device code is optimised by default)
$ nvcc -g -G -o program program.cu # with debug symbols
$ nvcc -lineinfo -o program program.cu # for profiling
$ nvfortran -o program program.cuf
$ nvfortran -fast -o program program.cuf # with optimisation (-fast bundles -O2 and vectorisation; -O3 is also accepted)
$ nvfortran -g -gpu=debug,lineinfo -o program program.cuf # debug
$ nvfortran -gpu=lineinfo -o program program.cuf # for profiling
In nvcc, -O only controls the host compiler; device code is optimised by default (-Xptxas -O3) and is un-optimised only when you pass -G.
To link CUDA libraries (e.g., cuBLAS):
$ nvcc -lcublas -o program program.cu
$ nvfortran -cudalib=cublas -o program program.cuf
Hardware and software requirements
An NVIDIA GPU with compute capability 7.5 or newer is recommended; compute capability 7.0 still works but its support is being phased out. Use CUDA Toolkit 12.x: CUDA 13 drops support for these older GPUs, so 12.x is both the floor and, for CC 7.0 hardware, the ceiling. CUDA Fortran requires the NVIDIA HPC SDK (nvfortran). Providing GPU access for a course run (workstations, a training cluster or scheduler-allocated nodes) is the responsibility of the site delivering the course; the number of participants is limited by the number of available GPUs and supervisors. Profiling on compute capability 7.0 is being phased out as well: Nsight Compute 2025.3 and Nsight Systems 2025.4 dropped Volta support, so to profile on such a device use the Nsight versions bundled with HPC SDK 25.7 or with the CUDA 12.x toolchain of later HPC SDKs (profiling is not needed for this module).
Running on a cluster¶
CUDA programs need an NVIDIA GPU to run. On a shared HPC system you typically:
Load the CUDA compiler/toolkit through your site’s module system.
Request a GPU through the site’s job scheduler (interactive or batch).
Compile and run your program on the allocated GPU node.
The exact commands (module names, scheduler, queue names) are site-specific — consult your system’s documentation. If your course is delivered on a specific system, your training provider will supply the corresponding setup instructions.
Keypoints
Use
nvccfor C/C++ CUDA code andnvfortranfor CUDA Fortran codeAdd
-O3/-fastfor optimisation of the host code,-g -G/-gpu=debugfor debugging, and-lineinfofor profilingLoading the CUDA toolkit and requesting a GPU is site-specific (see your cluster’s documentation)
Before you start the exercises
nvcc --version(for CUDA C/C++) ornvfortran --version(for CUDA Fortran) runs and reports a versionYou know which flag turns on optimisation, which adds debug symbols, and which prepares a build for profiling
You can reach a machine with an NVIDIA GPU — directly, or through your site’s job scheduler
You have compiled one program and run it on that GPU
See also
CUDA Toolkit Documentation — installation guides and
nvccreferenceNVIDIA HPC SDK Documentation —
nvfortranand CUDA Fortran