whitequark changed the topic of #yosys to: Yosys Open SYnthesis Suite: https://github.com/YosysHQ/yosys/ | Channel logs: https://libera.irclog.whitequark.org/yosys/ | Bridged to #yosys:matrix.org
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
emeb_mac has quit [Quit: Leaving.]
emeb_mac has joined #yosys
ec has quit [Remote host closed the connection]
ec has joined #yosys
notgull has quit [Ping timeout: 256 seconds]
notgull has joined #yosys
Martoni has joined #yosys
FabM has quit [Read error: Connection reset by peer]
emeb_mac has quit [Quit: Leaving.]
FabM has joined #yosys
FabM has quit [Changing host]
FabM has joined #yosys
Martoni has quit [Read error: Connection reset by peer]
lexano has quit [Ping timeout: 252 seconds]
lexano has joined #yosys
_whitelogger has joined #yosys
emeb_mac has joined #yosys
emeb_mac has quit [Quit: Leaving.]
FabM has quit [Remote host closed the connection]
emeb_mac has joined #yosys
<Zevv> I'm still having a very hard time interpreting critical path timing reports for my design
<Zevv> is there a general procedure to this, to properly learn and understand why and where this critical path originates from?
<Zevv> I'd love it to be highlighted in my dot graphs, for example
<lofty> Zevv: you mean the output of nextpnr?
<lofty> I mean, it prints the critical path.
<Zevv> yeah
<lofty> And even source locations.
<Zevv> I guess I just lack deep understanding of what I'm doing
nonchip has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nonchip has joined #yosys