<cr1901>
Did more monkeypatching- no, my linked code is definitely not a correct solution in general- I didn't guard against adding multiple layers of wrapper calls LOL)
hardkrash[m] has quit [Quit: Idle timeout reached: 172800s]
<whitequark[cis]>
you could probably just append #1000 to the VCD file as text
<cr1901>
whitequark[cis]: Maybe, but I'm kinda nerdsniped looking at the simulator internals anyway right now. There are worse uses of my time
<whitequark[cis]>
it has the advantage of not breaking when we improve the simulator (though, i don't recall if those delays are absolute--absolute ones would be more annoying)
<cr1901>
they're absolute
<cr1901>
(emphasis AFAICT)
<whitequark[cis]>
right. i guess a regex then or something >_>
<cr1901>
Or iterate over the file until the last clock entry w/ pyvcd, save it, then reopen the file for appending
<cr1901>
and add "#last_timestamp + 1000" to the end
<whitequark[cis]>
also works
<cr1901>
My current understanding is "when a testbench is finished, the clock process with the nearest edge will be schedule, and that causes the linked line to fire and extend the VCD until the next (active or inactive!) clock edge: https://github.com/amaranth-lang/amaranth/blob/main/amaranth/sim/pysim.py#L622
<cr1901>
When a testbench asserts, the clock process is never schedule (which makes sense), and the linked line will fire without having extended the VCD time
<cr1901>
>The way I've dealt with this is to click on the signal then arrow right to the very last signal transition. <-- this also works as a workaround
whitequark[cis] has quit [Ping timeout: 260 seconds]
whitequark[cis] has joined #amaranth-lang
vipqualitypost0[ has quit [Ping timeout: 260 seconds]
vipqualitypost0[ has joined #amaranth-lang
nyanotech has quit [Quit: No Ping reply in 180 seconds.]
nyanotech has joined #amaranth-lang
FFY00 has quit [Read error: Connection reset by peer]
FFY00 has joined #amaranth-lang
peepsalot has quit [Remote host closed the connection]
peepsalot has joined #amaranth-lang
FFY00 has quit [Read error: Connection reset by peer]
FFY00 has joined #amaranth-lang
FFY00 has quit [Read error: Connection reset by peer]
FFY00 has joined #amaranth-lang
notgull has joined #amaranth-lang
notgull has quit [Ping timeout: 268 seconds]
notgull has joined #amaranth-lang
<whitequark[cis]>
empirically, building a 10/100 MAC essentially from scratch, including a bunch of stream infrastructure, with Amaranth and Glasgow takes less than four days
<_whitenotifier-5>
[amaranth-lang/amaranth-lang.github.io] github-merge-queue[bot] 36c3b9e - Deploying to main from @ amaranth-lang/amaranth@09045a2724cee50f4d285066e8018d3a882d1785 🚀