PERFORMANCE Signal 75
Fedora 47 proposal reportedly to adopt Thin LTO for link-time optimization
↗
Illustration only Photo by Mika Baumeister on Unsplash
A Fedora 47 change proposal seeks to replace Fat LTO with Thin LTO to reduce memory use and speed up builds, potentially allowing more packages to use link-time optimization.
Thin LTO’s lower memory footprint can make large builds feasible on modest hardware, and faster compilation reduces developer turnaround time. If adopted, more Fedora packages could benefit from link-time optimizations without the resource costs of Fat LTO.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
A Fedora 47 proposal aims to switch the default from Fat LTO to Thin LTO.
Thin LTO is described as more memory efficient and provides faster build speeds.
The change is intended to enable broader use of LTO across Fedora packages.
THE READ
What the cluster adds up to.
The submitted change proposal for Fedora 47 would alter the link-time optimization strategy by using Thin LTO instead of Fat LTO. This represents a concrete shift in the compiler optimization pipeline for the distribution. The proposal is still under consideration and has not been merged into the release yet. Thin LTO is characterized as more memory efficient, meaning builds will consume less RAM than with Fat LTO. It also promises faster build speeds, which can shorten the time developers wait for compilation to finish. These benefits directly lower the resource cost of building large packages on typical development machines. The proposal notes a hope that more Fedora packages could also use Thin LTO. While the change could broaden LTO adoption, it does not guarantee that every package will switch, as some may still rely on features only available in Fat LTO. Consequently, packages that cannot use Thin LTO may continue to build with the existing approach. Adopting the proposal would require package maintainers to adjust their build configurations to enable Thin LTO. No new runtime dependencies are introduced, but the build environment must support the Thin LTO workflow. Until t
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER