Go 1.22 inlining overhaul (docs.google.com)
from tedu to golang@programming.dev on 27 Jul 2023 01:47
https://azorius.net/p/24n5gTgqp2PdkSlV9L

Our current inlining policy remains built on a foundation that is becoming increasingly strained as we add things like PGO, is increasingly anchored in past backend limitations, and it continues to use an overly simplistic cost model driven by an overly simplistic scheduler. Between unified IR and the untapped possibilities of PGO, I believe there’s now a significant opportunity to improve the inlining policy, resulting in significant performance improvements for Go applications, and reducing the effort and expertise needed to write highly efficient Go code.

#golang@programming.dev