emeb has quit [Quit: Leaving.]
X-Scale` has joined #yosys
dh73 has quit [Quit: Leaving.]
X-Scale has quit [Ping timeout: 245 seconds]
X-Scale` is now known as X-Scale
nrossi has joined #yosys
kraiskil has quit [Ping timeout: 265 seconds]
rohitksingh has quit [Ping timeout: 250 seconds]
ktemkin has joined #yosys
citypw has joined #yosys
X-Scale` has joined #yosys
X-Scale has quit [Ping timeout: 246 seconds]
X-Scale` is now known as X-Scale
<
tpb>
Title: Sci-Hub: устраняя преграды на пути распространения знаний (at sci-hub.tw)
<
whitequark>
EDA tools like Yosys and nextpnr focus on synchronous logic
<
promach3>
whitequark: are you familiar with structure of wavefront arbiter ?
<
whitequark>
I am not
dys has quit [Ping timeout: 276 seconds]
<
tpb>
Title: Wavefront arbiter - Wikipedia (at en.wikipedia.org)
<
whitequark>
I don't understand how it works, but cyclic combinatorial paths are essentially equivalent to asynchronous logic
<
whitequark>
a lot of existing tooling chooses not to bother with anything more complex than a latch (often latches too)
<
whitequark>
there are a few issues here. first, LUTs usually aren't glitchless, so techmapping combinatorial cycles correctly is hard
<
whitequark>
second, you have to somehow determine the worst case time for it settling to a fixpoint to provide timing analysis
FabM has joined #yosys
voxadam has quit [Max SendQ exceeded]
voxadam has joined #yosys
dys has joined #yosys
captain_morgan20 has quit [Read error: Connection reset by peer]
captain_morgan20 has joined #yosys
<
lukego>
whitequark: much obliged for the docs update :) I'll try to be such a good citizen too.
<
lukego>
emily: cool :)
FabM is now known as FabM_cave
jakobwenzel has quit [Quit: jakobwenzel]
fsasm has joined #yosys
pie_ has quit [Quit: No Ping reply in 180 seconds.]
pie_ has joined #yosys
pie_ has quit [Ping timeout: 252 seconds]
dys has quit [Ping timeout: 245 seconds]
indy_ is now known as indy
dys has joined #yosys
dh73 has joined #yosys
dys has quit [Ping timeout: 250 seconds]
dys has joined #yosys
citypw has quit [Ping timeout: 245 seconds]
tannewt has quit [Quit: Connection closed for inactivity]
pie_ has joined #yosys
dys has quit [Ping timeout: 246 seconds]
<
daveshah>
lukego: twitter thread for you haha
FabM_cave has quit [Quit: Leaving]
fsasm has quit [Remote host closed the connection]
fsasm has joined #yosys
kraiskil has joined #yosys
nrossi has quit [Quit: Connection closed for inactivity]
Jybz has joined #yosys
elGamal has joined #yosys
Jybz has quit [Quit: Konversation terminated!]
Jybz has joined #yosys
Jybz has quit [Remote host closed the connection]
dh73 has quit [Quit: Leaving.]
dh73 has joined #yosys
bobzoidting has joined #yosys
Stary has quit [Ping timeout: 250 seconds]
<
hackerfoo>
Does Yosys perform any numerical analysis e.g. optimize out any bits higher than the low N+1 of the result of adding two N bit inputs?
Stary has joined #yosys
<
mwk>
and that particular case is definitely handled
bobzoidting has quit [Read error: Connection reset by peer]
<
daveshah>
Several more complex cases aren't though
<
daveshah>
eg a+b-b may well not be optimised away
<
daveshah>
I think abc9 will usually work it out as it can see through the carry chains, in practice
<
daveshah>
Old abc won't if it is mapped to carries though
<
mwk>
it doesn't optimize even for plain "synth" to gates
<
daveshah>
synth uses some weird abc script that disables a lot of optimisations
<
daveshah>
I think if you do a normal "abc" after synth it optimises
fsasm has quit [Ping timeout: 246 seconds]
tpb has quit [Remote host closed the connection]
tpb has joined #yosys