The Wire · Showcase
COMPILER GETS SMARTER ABOUT FUNCTION ORDERING, BENCHMARK SUITE HITS BUILD SNAGS
By RepoJournal · Filed · About Go
Go's compiler now counts IR nodes to order functions more intelligently, while the benchmark harness stumbles on recent upgrades.
The compiler team landed a change that replaces statement-count heuristics with actual IR node counting during function compilation ordering [1]. This moves the needle on compile performance for large functions, though final numbers are still being benchmarked. Meanwhile, the benchmark suite hit friction after upgrading build targets: the Istio benchmark harness now invokes go build without an explicit output path, breaking when working directories shifted [2]. A follow-up fix is incoming to handle the Kubernetes builds that failed under the new go-build setup [3]. On the testing side, Alan Donovan landed a quick fix for a misspelled analyzer name in cmd/vet tests [4], keeping the vet suite clean heading into the next release cycle.
One email a day. Unsubscribe in one click.
Keep up with Go in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Watch benchmarks repo for Kubernetes build resolution in next CL golang/benchmarks [monitor]
- → Review compiler function ordering change for perf impact in your builds golang/go [plan]
References
- [1] cmd/compile: order functions by IR node count golang/go
- [2] sweet: upgrade go-build golang/benchmarks
- [3] sweet: upgrade benchmarks golang/benchmarks
- [4] cmd/vet: fix misspelled analyzer name in test golang/go