Skip to main content

Compile and build

A kernel is two sources compiled together. Tungsten describes what each processing element does; Paint describes where those elements sit and how colors route between them. The pair compiles to a machine image — a binary laid out over the fabric's address space — which is what the simulator and the hardware both run.

The languages themselves are documented in the Tungsten and Paint references. The pages here cover the machinery around them.

In this section​

  • Build and test framework — the flute model compiler's pattern rules, how a bench directory is organized, and how test.rc configurations become make TEST=N runs.
  • Machine image format — the binary format (header, blob, fragment) that loads a program and its data into the 3D fabric address space.
  • Debug information — the debuginfo.json schema mapping instructions to assembly, source locations, inline stacks, and the IR passes that produced them. This is the metadata the inspection tools read to relate machine state back to your source.

Where to start​

The tutorial's test infrastructure guide walks through a single example end to end — Makefile, test.rc, bench.paint, and ref.py — which is the fastest way to see the build in motion before reading the framework reference.