*** tpb <[email protected]> has joined #yosys | 00:00 | |
lofty | It's in times like these that I wish there was memoserv in libera | 01:35 |
---|---|---|
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? | 01:37 |
*** derekn <[email protected]> has quit IRC (Ping timeout: 276 seconds) | 05:46 | |
*** derekn <[email protected]> has joined #yosys | 05:56 | |
*** krispaul <[email protected]> has joined #yosys | 07:02 | |
*** kristianpaul <kristianpaul!~paul@user/kristianpaul> has quit IRC (Ping timeout: 264 seconds) | 07:04 | |
*** eater <[email protected]> has quit IRC (Ping timeout: 250 seconds) | 07:48 | |
*** peeps[zen] <peeps[zen]!~peepsalot@openscad/peepsalot> has quit IRC (Ping timeout: 252 seconds) | 07:55 | |
*** peepsalot <peepsalot!~peepsalot@openscad/peepsalot> has joined #yosys | 07:56 | |
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? | 16:21 |
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) | 16:22 |
tnt | Don't use icetime | 16:25 |
Zaba | Is it known to be unreliable? | 16:34 |
tnt | It's known to be broken. | 16:35 |
tnt | nextpnr includes much better timing code | 16:35 |
Zaba | OK that's good to know | 16:36 |
*** nonchip <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 22:11 | |
*** nonchip <[email protected]> has joined #yosys | 22:11 | |
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::e> has joined #yosys | 22:41 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!