nelgau has quit [Read error: Connection reset by peer]
nelgau has joined #yosys
ppisati has joined #yosys
killjoy has joined #yosys
killjoy has joined #yosys
peepsalot has quit [Quit: Connection reset by peep]
peepsalot has joined #yosys
<cr1901>
I don't have code to share immediately right now, but I found a load-bearing comment that when altered changes yosys' synth_ice40 LUT usage from 860 LUTs to 808 LUTs. Uhhh...
<lofty>
cr1901: amazing
<lofty>
which one? :p
<cr1901>
Not in yosys, in my design (generated from Amaranth). I would expect comments to uhhh... not change the synthesis results that much.
<cr1901>
Must be a next-gen optimization
FabM has joined #yosys
FabM has quit [Changing host]
FabM has joined #yosys
<cr1901>
Is there a way to change yosys' PRNG seed? Only thing I can think of, unless somehow "attribute enum_values" are special (seems like yosys and Amaranth just emit them, not use them)
<cr1901>
This is tomorrow me's problem
dormito has quit [Ping timeout: 258 seconds]
dormito has joined #yosys
bjorkint0sh has joined #yosys
bjorkintosh has quit [Ping timeout: 240 seconds]
bjorkint0sh has quit [Ping timeout: 258 seconds]
bjorkint0sh has joined #yosys
ec has quit [Remote host closed the connection]
ec has joined #yosys
cr1901_ has joined #yosys
cr1901 has quit [Ping timeout: 260 seconds]
bjorkint0sh has quit [Ping timeout: 248 seconds]
unkraut has quit [Remote host closed the connection]
unkraut has joined #yosys
<Myrl-saki>
`always @*` vs `assign` doesn't seem to always have the same behavior.
<Myrl-saki>
Heck, `if (p) begin q; r; end` is sometimes different as `if (p) q; if (p) r;`
<Myrl-saki>
What's the reason for this?
<lofty>
What do you mean by "same behaviour"?
<Myrl-saki>
Right, that was a bit vague lol sorry. I mean that it doesn't have the same resource usage.
<lofty>
Well, you do have to consider that Yosys is chaotic; small changes in the source code can have pretty big changes elsewhere
<lofty>
Due to things like hashing and such
arogora has joined #yosys
<Myrl-saki>
Ahh thanks. And yeah, I see. So from the PoV of Yosys (as a graph? or RTL?), they're basically the same, but the order that things get applied differ, thus resulting in different resource usage?
<lofty>
Yeah
killjoy has quit [Ping timeout: 252 seconds]
arogora is now known as killjoy
killjoy has quit [Changing host]
killjoy has joined #yosys
<lofty>
A big factor in this is, for example, that Yosys carries source code information around
<lofty>
Like where a cell was defined
<Myrl-saki>
Yeah, I see now. Even changing the order of the assigns change the behavior lol
<Myrl-saki>
Err, not behavior.
bjorkintosh has joined #yosys
bjorkintosh has quit [Changing host]
bjorkintosh has joined #yosys
<Myrl-saki>
This is not exactly related, but I feel like I'm getting a very huge "told you so" moment since my shifter is actually the critical path right now. :x
<Myrl-saki>
Now I'm curious how much the order matters!
<Myrl-saki>
Wild, I think changing the order worked.
xiretza[cis] has joined #yosys
<xiretza[cis]>
for some definition of "worked"
<Myrl-saki>
Hm, why does it say the critical path is slower, but the frequnecy can be higher?
dys has quit [Remote host closed the connection]
<lofty>
You're going to have to provide more information than that :p