Snapshotmaster · 72aa6db
A Go program's path from `go build` through native linking, then through goroutines, GC, and network polling at runtime.
Click a building or route
System map8 components · 9 connections
130%
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal
Terms, in plain English
Package action graphA dependency graph of compile, archive, and link steps needed to produce the requested Go target.
How to study this repo
- 1Build one tiny package
Run `go build -x` and match the printed compile/link commands to cmd/go/internal/work/build.go.
- 2Learn G-M-P visually
Read runtime/proc.go's scheduler comments, then sketch how two Ps can run many goroutines across changing Ms.
- 3Connect I/O and GC
Trace how netpoll returns ready goroutines and how concurrent mark workers compete for the same scheduler processors.