Julian Oppermann

I have done this in a limited fashion in an internal tool. I'll put up the code in a draft PR for further discussion.

CC: @rsetaluri @leonardt

Turned out that #3170 wasn't the right way to this. The FIRRTL dialect already provides some form of structure flattening, but unfortunately I don't have the time right now to...

> For shr and shl, how would they differ from the existing comb operators? I think the main reason for having `hwarith` shifts is that the `comb` operators don't accept...

+1 on the idea, though I wouldn't coin this as an import/export format from/to SSP. I think what you're describing is more like a "one-sided scheduler": 1) take a `Problem`...

Awesome! Looks good on a very quick first glance. I'm currently away from my desk unfortunately, but I will do a detailed review early next week. This should probably be...

Awesome, count me in to help! My knowledge of SMT is also basically just that this framework exists and is a viable approach for scheduling, but I haven't had time...

`%g1` should be `%s0_valid`, right?

Intriguing design! One question though: I assume the "middle" IR (w/ stages, w/o regs) is intended to conveniently transform the pipeline by moving around ops between stages. Given that the...

> > "retimeable" -- it's a misnomer. What are you "timing" again? > > Naming is hard. Retimeable seemed like a good fit since the `pipeline.stage` operations can be freely...