tpb has quit [Remote host closed the connection]
tpb has joined #yosys
philtor has quit [Remote host closed the connection]
philtor has joined #yosys
bjorkintosh has quit [Quit: Leaving]
bjorkintosh has joined #yosys
notgull has quit [Ping timeout: 246 seconds]
notgull has joined #yosys
<
st3llar>
wasted a few hours experimenting, but the answer was in the suggested (* no_rw_check *)
<
st3llar>
the extra circuitry is to ensure read-first or write-first behaviour
<
tpb>
Title: Memory Inference Patterns - Google Docs (at docs.google.com)
st3llar has quit [Ping timeout: 245 seconds]
<
lofty>
what was the point of fixing Yosys to correctly handle this if people will forever reach for the "I want to cause bugs" switch...
st3llar has joined #yosys
st3llar has quit [Client Quit]
st3llar has joined #yosys
<
st3llar>
just learning, and now I can appreciate yosys even more :)
Psentee has quit [Quit: Off]
Psentee has joined #yosys
Psentee has quit [Quit: Off]
Psentee has joined #yosys
Psentee has quit [Quit: Off]
Psentee has joined #yosys
<
lofty>
st3llar: so, if you use that attribute you technically have a simulation/synthesis mismatch
<
lofty>
By the way, instead of relying on internal Google docs that I may or may not have leaked
<
tpb>
Title: 10. Memory mapping (at yosyshq.readthedocs.io)
<
lofty>
(and that documentation started out as a blog post I was going to make)
<
st3llar>
oups i somehow forgot about the manual, thanks a lot!
nelgau has quit [Read error: Connection reset by peer]
nelgau_ has joined #yosys
nelgau_ has quit [Read error: Connection reset by peer]
nelgau has joined #yosys
nelgau has quit [Ping timeout: 240 seconds]
nelgau has joined #yosys
schaeg has joined #yosys
schaeg_ has joined #yosys
schaeg has quit [Ping timeout: 256 seconds]
st3llar has quit [Quit: leaving]
schaeg_ has quit [Ping timeout: 256 seconds]
schaeg has joined #yosys
nonchip has joined #yosys
_whitelogger has joined #yosys
Lord_Nightmare has joined #yosys