00:05 <zyp[m]> Because a big part of the simulator change was to give a way to differentiate between signal state at the edge and signal state after the edge

01:39 <cr1901> zyp[m]: Okay. So until() samples the values just before the current clock edge takes effect?

01:40 <cr1901> and an explicit "ctx.tick(); ctx.get()" gets the values after the clock edge?

01:42 <cr1901> (I could be dense, but I don't see anything in the docs suggesting a "while ctx.get(): ctx.tick()" and "ctx.tick().until()" are semantically different. It looks like I just never wrote a testbench where the difference mattered until now)

01:57 <zyp[m]> See .sample()

01:58 <zyp[m]> You probably want that rather than ctx.get()

02:06 <cr1901> zyp[m]: Btw, to answer your q about litex- yes every CPU does interrupts differently. I was looking for a way to avoid modifying Sentinel b/c I don't want it to be configurable :P.

02:07 <cr1901> Yea I don't really use .sample() it seems, not in smolarith at least (which means none of my testbenches care about the difference)

02:19 <cr1901> Anyways you're correct, sample does mention the difference (it samples at the leading edge, which must mean get() samples at the trailing edge/after propagation at the current simtime.)