https://segflow.github.io/tags/escape-analysis/Recent content in Escape Analysis on SegflowHugoen-usSun, 17 Apr 2022 14:45:00 +0100https://segflow.github.io/post/escape-analysis-examples/Sun, 17 Apr 2022 14:45:00 +0100https://segflow.github.io/post/escape-analysis-examples/<p>A while back I had a hot loop that profiled like a heap-allocation machine gun. <code>pprof</code> blamed <code>runtime.mallocgc</code>. The code looked innocent. The fix turned out to be a one-line signature change, and the compiler had been quietly screaming at me about it the whole time via <code>-gcflags=-m</code>.</p> <p>This post is the second half of a tour I started in <a href="../../post/go-compiler-optimization/">My journey optimizing the Go Compiler</a> and continued in <a href="../../post/inlining-budgets/">What actually fits in Go&rsquo;s inlining budget</a>. Inlining decides <em>where</em> code runs; escape analysis decides <em>where data lives</em>. Six 10-line examples cover roughly 90% of what you&rsquo;ll see in real Go.</p>