ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #gcc
Learn how GCC’s Link-Time Optimization (-flto) enables whole-program inlining and dead-code elimination, reducing binary size and improving runtime, along with its trade-offs and verification steps.
GCC's -Wmaybe-uninitialized only fires under optimization and mixes real bugs with false positives. A diagnostic guide to triaging, fixing, and knowing when to restructure.
How to use -ffunction-sections, -fdata-sections and --gc-sections to strip unused code and shrink embedded binaries.
An architecture note on GCC Link-Time Optimization: requirements, minimal design, trust/data boundaries, operational checks, failure modes, and conditions that would change the design.
Is -O3 always faster than -O2? Explore the trade-offs between loop vectorization, binary bloat, and I-cache performance to decide which GCC optimization level fits your project.
Learn how to use GCC's __attribute__((section)) and linker scripts to precisely place code and data in specific memory regions to optimize RAM and Flash usage in embedded C.
Learn how to enable GCC's profile-guided optimization with -fprofile-generate and -fprofile-use, see a simple example, and avoid common pitfalls.
A diagnostic guide for GCC 7–13 Link-Time Optimization failures: recognize undefined reference and multiple definition errors, trace root causes through symbol visibility, ODR flag mismatches, and mixed LTO/non-LTO objects, then apply targeted fixes with version-aware commands.
Learn how GCC’s PGO lets the compiler reorder code and inline functions based on actual execution data, giving measurable speedups without source changes.
c
embeddedc