omnitechnomancer has quit [Ping timeout: 240 seconds]
omnitechnomancer has joined #apicula
<pepijndevos_>
welp, getting some weird issues... maybe uninitialised memory or some pointer that got into a IdString :(
<daveshah>
valgrind it
<pepijndevos_>
how?
<pepijndevos_>
also lol:
<pepijndevos_>
Info: port cpu.cpuregs.regs[11][20]_DFFE_Q_DFFLC.I2, connected to net 'cpu.reg_pc[22]_LUT4_I1_I2[2]', has timing budget of 340282346638528859811704183484516925440.000000ns
<daveshah>
usually valgrind will tell you if you are relying on uninitialised memory
<pepijndevos_>
that's 0xffffff00000000000000000000000000 in hex
<pepijndevos_>
usually you have to run valgrind with a particular tool right
<daveshah>
i just the default one for this kind of stuff
<pepijndevos_>
alright
<daveshah>
it will spew a load of crap at the start from python, you can either ignore that or find the flag to not print stuff coming from that so
<daveshah>
or build without python
<pepijndevos_>
trying...
<pepijndevos_>
I forgot how slow valgrind is...
<pepijndevos_>
seeing lots of ==25727== Invalid read of size 4
<pepijndevos_>
==25727== at 0x1866B0: nextpnr_gowin::Context::checksum() const (nextpnr.cc:366)
<pepijndevos_>
yea, probably my initialization is all wrong...
<daveshah>
I think what is probably happening is a reference to a deleted cell is remaining on a net
<pepijndevos_>
hmmmm okay, so that could be for example packing deleting a cell, but missing one of its inputs?
<pepijndevos_>
Yea what's probably happening... the Gowin DFF cells have LSR and CE, but the generic DFF does not, so I forgot to deal with those inputs.