LUT treemap: which submodule eats your LUTs, from yosys stat -json

Drop yosys stat -json from a run without -flatten: a treemap of LUTs or FFs per submodule, each times its instance count, beside the flattened total. Read in your browser.

A file you open here is read by your browser only: it is never uploaded. The page sets no cookie and sends nothing anywhere.

Where the numbers come from

Yosys 0.67+post (git sha1 b8e7da6f40ae8f552c116bf6c359b07c6533e159), run by scripts/widget-data/lut-treemap.mjs in a scratch directory: nice -n 10 yosys -q -p "read_verilog gf16_add.v gf16_mul.v gf16_dot4_p.v gf16_matmul4x4_p.v; synth_xilinx -top gf16_matmul4x4_p; tee -q -o stat.json stat -json"
the same command with synth_xilinx -flatten -top gf16_matmul4x4_p, written to flat.stat.json, for the flattened total
gHashTag/trinity fpga/gf16-pipelined/gf16_dot4_p.v and gf16_matmul4x4_p.v at commit df6cb3e0f654; gHashTag/t27 fpga/vivado/gf16_add.v and gf16_mul.v at commit ea15cd54c8c9; read with git show, sha256 of each in sample.json
public/widgets/lut-treemap/sample.stat.json and sample.flat.stat.json: the yosys output, byte for byte; sample.json: commands, yosys -V line, exit codes, seconds, input and output sha256
public/widgets/lut-treemap/treemap.js: the one parser, instance multiplier and treemap layout, run in node for the sample and in the browser for your file; card.png is drawn from sample.json by scripts/widget-data/lut-treemap-card.py
node scripts/widget-data/lut-treemap.mjs --check: re-reads both stat files and fails if any K_SAMPLE_ fact in this spec disagrees; scripts/widget-data/lut-treemap-paramod.v is the parser fixture for $paramod names

This widget's .t27 source · All widgets