<promach_>
ZipCPU: you mean even if the trace does not show that it failed, it is still due to bugs in my code ?
X-Scale has joined #yosys
seldridge has joined #yosys
promach_ has quit [Quit: WeeChat 2.2]
<ZipCPU>
promach_: How long is your trace?
<ZipCPU>
Nevermind ... it's an induction failure.
<ZipCPU>
I have never seen an example of a design failing induction that didn't show the error in the trace.
<promach>
ZipCPU: let me check through my code again. sigh, multiclock induction needs more debugging than the normal single-clock induction
<promach>
ZipCPU: wish me luck in finding out the bug !
altenius has quit [Ping timeout: 248 seconds]
seldridge has quit [Ping timeout: 264 seconds]
dys has joined #yosys
leviathan has joined #yosys
kraiskil has joined #yosys
dys has quit [Ping timeout: 268 seconds]
dys has joined #yosys
dys has quit [Ping timeout: 265 seconds]
kraiskil has quit [Read error: Connection reset by peer]
kraiskil has joined #yosys
gnufan has left #yosys [#yosys]
rqou has quit [Remote host closed the connection]
rqou has joined #yosys
mwk has quit [Ping timeout: 240 seconds]
mwk has joined #yosys
proteusguy has quit [Ping timeout: 256 seconds]
gnufan has joined #yosys
proteusguy has joined #yosys
digshadow has quit [Quit: Leaving.]
digshadow has joined #yosys
massi has joined #yosys
kraiskil has quit [Read error: Connection reset by peer]
kraiskil has joined #yosys
<ZipCPU>
promach: I think I recall telling you before you started your multiclock induction proof that my own multiclock proof of a serial port was the hardest proof I had done.
<ZipCPU>
Perhaps you need to try proving some simpler things and come back to multiclock later, once you've learned to trust the tools more.