rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has joined ##openfpga
Asu has joined ##openfpga
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
Mimoja has quit [Quit: Ping timeout (120 seconds)]
gsi__ has quit [Ping timeout: 248 seconds]
gsi_ has joined ##openfpga
nickjohnson has quit [Ping timeout: 248 seconds]
nickjohnson has joined ##openfpga
emily has quit [Quit: Updating details, brb]
emily has joined ##openfpga
mifune has quit [Ping timeout: 252 seconds]
mifune has joined ##openfpga
gnufan_home1 has joined ##openfpga
gnufan_home has quit [Ping timeout: 272 seconds]
rohitksingh_work has quit [Read error: Connection reset by peer]
ondrej3 has quit [Quit: Leaving]
vonnieda has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
rohitksingh has joined ##openfpga
carl0s has joined ##openfpga
Dolu1 has joined ##openfpga
genii has joined ##openfpga
vonnieda has joined ##openfpga
emeb has joined ##openfpga
Asu has quit [Ping timeout: 258 seconds]
Asu` has joined ##openfpga
vonnieda has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Asu has joined ##openfpga
Asu` has quit [Ping timeout: 244 seconds]
vonnieda has joined ##openfpga
rohitksingh has quit [Ping timeout: 248 seconds]
flea86 has quit [Quit: Goodbye and thanks for all the dirty sand ;-)]
octycs has joined ##openfpga
rohitksingh has joined ##openfpga
gnufan_home1 has quit [Ping timeout: 252 seconds]
Dolu1 has quit [Ping timeout: 248 seconds]
gnufan_home has joined ##openfpga
Asu` has joined ##openfpga
Asu has quit [Ping timeout: 248 seconds]
rombik_su has quit [Ping timeout: 248 seconds]
Dolu1 has joined ##openfpga
Dolu1 has quit [Ping timeout: 248 seconds]
ironsteel has quit [Quit: Ex-Chat]
m4ssi has quit [Remote host closed the connection]
rohitksingh has quit [Ping timeout: 245 seconds]
vonnieda has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
vonnieda has joined ##openfpga
<ZipCPU>
ZirconiumX: I typically do worry about UNOPTFLAT warnings in my own designs. You can typically get around them by placing the item in question into an always @(*) block, and then ordering the logic the way you want it
<ZipCPU>
When it's someone else's designs ... usually I'm only looking for bugs prior to verification, so I might ignore them then. Otherwise it probably depends upon what the bug is to know how significant the problem is
<ZipCPU>
Worst case: Verilator simulation won't match your design as implemented in hardware. Best case? The warning was irrelevant.
<ZipCPU>
As for dumping things to VCD files, I cover that on my blog. As for dumping other things, I typically do that from C++.
<kc8apf>
sensille: what programmer? If I don't already have one, I'll gladly receive it
<ZirconiumX>
ZipCPU: this goes through an @* block though
<ZipCPU>
Are all of the associated unoptimizable flat values in the same @* block? That would then tell Verilator how to optimize them