Skip to main content

Tools and debugging

A kernel passes through three stages: it is compiled and laid out, it runs on the fabric simulator, and its behavior is inspected when the result is not what you expected. The tooling is grouped the same way.

Editor extensions​

Edit .w and .paint files with the Vim and Visual Studio Code integrations the toolset ships. They provide language-aware file detection and syntax highlighting, with Tungsten snippets available in Visual Studio Code.

Compile and build​

Turn .w and .paint sources into a machine image, and understand what the compiler recorded about it.

Build and test framework · Machine image format · Debug information

Simulate​

Run the image on the fabric simulator, put data in, and take results out.

miset and miget · Pipeline traces

Debug and inspect​

Find out what the fabric actually did — per tile, per cycle, per color.

Portrait · meminsp · Filter debugging

Working guides​

These guides show how the tools fit into a session rather than what each flag does:

  • Debugging kernels — the debugging checklist and worked scenarios for comparison failures, timeouts, wrong values, routing problems, switch positions, floating-point mismatch, and message passing.
  • Test infrastructure — how a test directory fits together.
  • Architecture notes — the hardware behavior the tools expose.