ChanServ changed the topic of #yosys to: Yosys Open SYnthesis Suite: https://github.com/YosysHQ/yosys/ | Channel logs: https://libera.irclog.whitequark.org/yosys/
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
<lofty> It's in times like these that I wish there was memoserv in libera
<lofty> I don't suppose somebody could point so-offish to https://github.com/YosysHQ/yosys/blob/a14dec79ebc85fae807684fa027d8098a16a4d34/docs/source/CHAPTER_CellLib.rst#binary-operators and the section on $shift and $shiftx could they?
derekn has quit [Ping timeout: 276 seconds]
derekn has joined #yosys
krispaul has joined #yosys
kristianpaul has quit [Ping timeout: 264 seconds]
eater has quit [Ping timeout: 250 seconds]
peeps[zen] has quit [Ping timeout: 252 seconds]
peepsalot has joined #yosys
<Zaba> Hello. Does anybody know how to interpret an icetime report that says "Total path delay: 10000xx.xx ns (0.00 MHz)" and in which the critical path starts with loop-start, for a design with no obvious logic loops or inferred latches?
<Zaba> I've posted a simple reproducer as a comment here a while back https://github.com/YosysHQ/icestorm/issues/114 (the original report seems to have a more obvious design issue leading to this)
<tnt> Don't use icetime
<Zaba> Is it known to be unreliable?
<tnt> It's known to be broken.
<tnt> nextpnr includes much better timing code
<Zaba> OK that's good to know
nonchip has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nonchip has joined #yosys
so-offish has joined #yosys