It is probably fair to conclude that naming this dialect `StaticLogic` has been a pain point for a while. This commit proposes a dialect renaming to `Pipeline`, for a couple of reaons:
1. So far, we've only been working with pipeline abstractions within this dialect.
2. Pipeline representations aren't necessarily statically scheduled - we plan on adding switches to select between latency sensitive and latency insensitive lowerings of pipelines.
This name change does not preclude renamings in the future if we want to fit more stuff into this dialect. Personally, i think it is prudent to maintain a dialect name which reflects what's actually being done within the dialect, as well as the (near/mid/"someone actually intends to work on this"-term) future plans for the dialect.
Seeing as quite a few new dialects and conversions have entered CIRCT since this diagram was made, I think it's due for an update! Let me know what you think, and if you have anything you'd like to have added/removed.
This makes sure not to rename FIRRTL to HWRTL :-), and I spot checked a
many things to avoid changing general references to RTL (e.g. when referring
to external tools) but I suspect that I missed some. Please let me know (or
directly correct) any mistakes in this mechanical patch.
After the addition of the LowerTypes pass to the FIRRTL dialect, the
lowering passes within FIRRTL are no longer hypothetical, and the path
from high/mid-FIRRTL to low-FIRRTL is a solid (albeit thin) line.
Morten Borup Petersen