Documentation

[sequencer]

The current uArch of T1 is not a micro arch now, appending to a lot of parameters, it is going to be another giant
In order to deliver this to opensource community as well as commercial customers, we need a sophisticated documentation flow.
I'm proposing using Typst as documentation template, using C-API extract Property from generated MLIR, here is the flow we need:

• For each T1 Module, An architecture documentation should be provided, it may or may not consume parameter(OM-like), cc @SharzyL
• A Parameter extractor for MLIR like Python Binding in CIRCT, cc @SpriteOvO

[DecodeTheEncoded]

Hi @sequencer , Thanks for what you done for the commnity, I wonder if there are in-depth documentation(papers, tutorials or talks) about T1?

[sequencer]

Working on the paper :melting face: