HPC Software Stack Optimization is the systematic process of extracting maximum performance from HPC applications through the entire software stack — from compiler flags and auto-vectorization through mathematical library selection, memory allocator tuning, and runtime configuration — recognizing that optimal hardware utilization requires attention to every layer from application code to hardware firmware, with each layer potentially contributing 2-10× performance differences.

Compiler Optimization Flags

The compiler is the first optimization layer:

• -O3: enables all safe optimizations (loop unrolling, function inlining, vectorization). Baseline for production HPC.
• -march=native: enable all CPU features (AVX-512 on Skylake-X/Ice Lake, SVE on ARM Neoverse). Binary tied to specific CPU family.
• -ffast-math: relax IEEE 754 strictness (allow reassociation, assume no NaN/Inf). Enables vectorization of reductions. Warning: may change floating-point results.
• -funroll-loops: explicit loop unrolling (compiler heuristic may not unroll aggressively enough).
• -flto (Link-Time Optimization): cross-module inlining and optimization (significant gain for modular code).
• -fprofile-use (PGO): use runtime profile to guide inlining, branch prediction, loop optimization — typically 5-15% gain.

Auto-Vectorization

• AVX-512 (Intel Ice Lake/Sapphire Rapids): 512-bit SIMD, 16 floats/8 doubles per instruction. Enable with `-mavx512f`.
• ARM SVE (Scalable Vector Extension, Fugaku/Grace): variable-length SIMD (128-2048 bits), code is length-agnostic.
• Vectorization reports: `-fopt-info-vec (GCC) or -qopt-report` (Intel) explain which loops vectorized and why not.
• Obstacles: pointer aliasing (resolve with `restrict`), function calls in loop bodies, non-unit stride access, complex control flow.

Vendor vs Open-Source Compilers

Mathematical Libraries

• Intel MKL (oneAPI MKL): BLAS, LAPACK, FFTW interface, ScaLAPACK. Highly optimized for Intel CPUs. Free.
• OpenBLAS: open-source, competitive with MKL on AMD CPUs. Default for many Linux distributions.
• AMD AOCL (BLIS, libFLAME, FFTW): AMD-optimized math libraries (AMD EPYC).
• FFTW: gold standard for FFT, self-tuning (generates plan at startup).
• cuBLAS/cuFFT/cuDNN: NVIDIA GPU math libraries (essential for GPU computing).

Runtime Environment Tuning

• `OMP_NUM_THREADS, OMP_PROC_BIND=close, OMP_PLACES=cores`: thread affinity for NUMA-aware placement.
• `GOMP_SPINCOUNT`: spin-wait duration before sleep (latency vs power).
• Memory allocator: jemalloc/tcmalloc reduce fragmentation vs glibc malloc for multi-threaded apps.
• Huge pages (2MB vs 4KB): reduce TLB misses for large working sets (`/proc/sys/vm/nr_hugepages`).
• MPI binding: `--bind-to core/socket` ensures MPI ranks are NUMA-local.

HPC Software Stack Optimization is the engineering discipline that extracts the full potential of expensive supercomputer hardware through careful attention to every software layer — transforming the same application code from 20% to 90% of peak hardware efficiency through systematic compiler, library, and runtime tuning.