V8pedia

Primary sources & further reading

V8pedia is a map; the source is the territory. This page collects the primary sources — the actual code and official docs — so you can verify everything here and keep reading past where this site stops.

::: warning Unofficial V8pedia is an unofficial community project. Nothing here is authoritative. When this site and the sources below disagree, the sources are right. :::

The pinned source tree

Every source link on this site points at one frozen commit, so the links never rot and the line numbers stay aligned:

To read the current code, replace the commit hash in any permalink with main (on the googlesource mirror) — but expect drift from what's described here.

The directories that own each subsystem

A contributor's mental index of the tree, mapped to V8pedia sections:

Directory Owns V8pedia
src/parsing/ scanner, parser, preparser Parser
src/ast/, src/zone/ AST, zone allocator Parser
src/interpreter/ Ignition: bytecode, generator, handlers Ignition, Bytecode
src/baseline/ Sparkplug baseline JIT Sparkplug
src/maglev/ Maglev mid-tier compiler Maglev
src/compiler/ TurboFan (Sea of Nodes, pipeline) TurboFan
src/execution/ isolate, tiering manager Isolates, Feedback
src/deoptimizer/ deoptimization Deopt
src/ic/ inline caches, stub cache Inline caches
src/objects/ Map, descriptors, feedback vector, SFI Map, ICs
src/heap/ Orinoco GC GC
src/builtins/, src/torque/, src/codegen/ builtins, Torque, CSA Builtins
src/snapshot/ startup & context snapshots Isolates
src/sandbox/ the V8 sandbox Sandbox
src/flags/flag-definitions.h every runtime flag + default Feedback
src/d8/ the d8 developer shell d8

Official documentation

How to verify a claim on this site

  1. Click the permalink next to the claim.

  2. Read the surrounding code — not just the quoted lines.

  3. Cross-check the current behavior by swapping the commit for main.

  4. Confirm dynamic behavior empirically in d8 with the relevant --trace-* flag.

  5. If it's wrong or stale, that's the most valuable thing you can report.

Contributing to V8 itself

V8 development happens on Gerrit (chromium-review.googlesource.com), not GitHub pull requests (GitHub is a read-only mirror). Start from v8.dev/docs/contribute. The path this site aims to put you on: read a subsystem here → read its directory above → build with gm.py → experiment in d8 → pick up a bug.

See also