ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #gcc
GCC link-time optimization lets the compiler inline functions across separate C files and remove unused code, but it trades link time and memory for smaller binaries.
GCC -flto enables whole-program optimization across object files, but it slows linking and complicates debugging. Here is how to decide and verify.
When a branch in performance-critical C code runs hot, __builtin_expect tells GCC the likely path—but only use it for predictable branches and verify the impact with assembly or profiling.
Thin LTO gives most whole-program optimization benefits with manageable link-time cost. Enable -flto=thin -O2 on both compile and link lines, install the linker plugin, audit for latent UB, and expect 3-7% speedup on cross-file hot paths.
Learn how to use GCC's __builtin_expect to optimize branch prediction for hot paths, reducing pipeline stalls and improving performance in critical code sections.
GCC's -flto lets the linker optimize across translation units, often shrinking release binaries at the cost of longer link times.
Learn how GCC's Link-Time Optimization lets the compiler inline functions and eliminate dead code across translation units, and see the trade‑offs in build time, binary size, and debugging.
Learn how GCC’s -fanalyzer static analysis pass can detect double‑free and similar memory bugs at compile time, with a concrete example, setup steps, and practical trade‑offs for CI use.
ARM64 Pointer Authentication (PAC) signs pointers to detect tampering before use. Learn how to enable PAC in GCC/Clang, verify hardware support, and measure its impact on aarch64 systems. The guide includes code, verification steps, and trade‑off analysis.
c
aarch64