GCC 15 series advances: C23 default, better diagnostics, incremental LTO and wide toolchain upgrades

Key update

The GCC 15 release series (15.1 introduced the major language and toolchain changes; 15.2 is a bug‑fix followup) makes the C frontend default to C23 and brings a broad set of practical improvements: incremental LTO (reduces rebuild time for small edits), richer diagnostics (colorized diffs, SARIF output and new -fdiagnostics-add-output options), better vectorization and large‑file compile performance, expanded OpenMP/GPU offload support, and ongoing C++ standard adoption and std::format / module work — all aimed at real build and CI workflows rather than purely academic features. (gcc.gnu.org)

Why it matters

If your toolchain or CI images are not intentionally pinned, switching compilers to a distro shipping GCC 15 can change default semantics (C now targets C23), which can expose subtle compatibility breakages or change behavior for undefined/implementation‑specific code; pin -std=gnu17/gnu11 (or explicitly target gnu23) in builds if you need stability. Incremental LTO and compile performance fixes materially reduce edit‑compile cycles for large C/C++ codebases and LTO users, so upgrading can speed developer iteration and CI costs. The new diagnostics and SARIF support make machine‑consumable error reporting practical for automation (CI, SAST pipelines) without brittle custom parsers. OpenMP/GPU offload and improved vectorization are concrete wins for numerical/HPC teams wanting better upstream toolchain support instead of fragile custom toolchains. In short: test builds on GCC 15 in CI, update build flags where you rely on older defaults, and consider upgrading CI images and distro toolchains to benefit from faster rebuilds and better machine‑readable diagnostics. (gcc.gnu.org)

Source

• Source