clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
emeb has left #yosys [#yosys]
emeb_mac has joined #yosys
rohitksingh has quit [Remote host closed the connection]
rohitksingh has joined #yosys
citypw_ has joined #yosys
rohitksingh has quit [Ping timeout: 260 seconds]
rohitksingh has joined #yosys
rohitksingh has quit [Ping timeout: 265 seconds]
nengel has quit [Ping timeout: 246 seconds]
nengel has joined #yosys
voxadam has quit [Read error: Connection reset by peer]
voxadam has joined #yosys
Jybz has joined #yosys
rohitksingh has joined #yosys
Jybz has quit [Quit: Konversation terminated!]
nengel has quit [Ping timeout: 240 seconds]
nengel has joined #yosys
emeb_mac has quit [Quit: Leaving.]
adjtm_ has quit [Ping timeout: 260 seconds]
jakobwenzel has joined #yosys
dys has joined #yosys
fsasm has joined #yosys
vidbina has joined #yosys
stzsch has quit [Ping timeout: 246 seconds]
peepsalot has quit [Ping timeout: 240 seconds]
finnb has quit [Excess Flood]
finnb has joined #yosys
cr1901_modern has quit [Ping timeout: 268 seconds]
nengel has quit [Ping timeout: 246 seconds]
cr1901_modern has joined #yosys
like2wise has joined #yosys
vidbina has quit [Ping timeout: 265 seconds]
fsasm has quit [Ping timeout: 265 seconds]
develonepi3 has joined #yosys
az0re has quit [Remote host closed the connection]
vidbina has joined #yosys
citypw_ has quit [Ping timeout: 272 seconds]
vidbina has quit [Ping timeout: 240 seconds]
dh73 has joined #yosys
fsasm has joined #yosys
rohitksingh has quit [Ping timeout: 240 seconds]
dys has quit [Ping timeout: 240 seconds]
rohitksingh has joined #yosys
rjo has quit [Ping timeout: 246 seconds]
promach3 has quit [Ping timeout: 246 seconds]
fevv8[m] has quit [Ping timeout: 252 seconds]
Thorn has quit [Ping timeout: 265 seconds]
emily has quit [Ping timeout: 248 seconds]
nrossi has quit [Ping timeout: 240 seconds]
jryans has quit [Ping timeout: 240 seconds]
pepijndevos[m] has quit [Ping timeout: 240 seconds]
rjo has joined #yosys
nengel has joined #yosys
nrossi has joined #yosys
pepijndevos[m] has joined #yosys
fevv8[m] has joined #yosys
kuldeep has quit [Read error: Connection reset by peer]
rohitksingh has quit [Ping timeout: 272 seconds]
jryans has joined #yosys
jryans has quit [Excess Flood]
vidbina has joined #yosys
nrossi has quit [Quit: killed]
fevv8[m] has quit [Quit: killed]
rjo has quit [Quit: killed]
pepijndevos[m] has quit [Quit: killed]
<ZirconiumX> dh73: I unintentionally reinvented parts of your yosys-bench branch while trying to write something similar-ish
<ZirconiumX> But there are bits that you might want to consider
emily has joined #yosys
<dh73> Well, thank you. Those scripts was for a very specific tasks but is in the todo list to make them much better, so any input on that will be for sure considered
<ZirconiumX> It seems your script is more or less "how well does this do in general", whereas mine is "how do these two versions compare?"
<ZirconiumX> So I'm using what I believe to be the right tool for the job: a sequential probability ratio test
X-Scale` has joined #yosys
X-Scale has quit [Ping timeout: 240 seconds]
<dh73> Pareto?
X-Scale` is now known as X-Scale
<ZirconiumX> Which means I can compare two versions and minimise the average running time while keeping bounded error
<dh73> Pareto images between implementation of design space?
<ZirconiumX> Wald, actually :P
<tpb> Title: Sequential probability ratio test - Wikipedia (at en.wikipedia.org)
<ZirconiumX> (but a generalised version of this)
<dh73> I see. Also yes, those scripts are just to compare current implementations without a record. Your approach sounds good. Since Nina added the scratchpad for abc, one of the future implementations of the benchmark suite is to have data of QoR among Yosys versions. I think is a very good tool to have
<ZirconiumX> As a data point, I can reject ABC9 as at most no better than ABC1 for iCE40 in 49 place-and-routes
<ZirconiumX> Which is not that much CPU time actually
<daveshah> > As a data point, I can reject ABC9 as at most no better than ABC1 for iCE40 in 49 place-and-routes
<daveshah> presumably only for a few designs?
<ZirconiumX> At the moment I'm only testing picorv32_large.v, so potentially
<ZirconiumX> It'd be feasible to round-robin the scripts while testing
<ZirconiumX> Although Yosys seems to crash on things like OpenSPARC
<daveshah> Certainly my experience of ABC9 for ECP5 is that it made a few designs worse and more designs better
<daveshah> I have had OpenSPARC work with Yosys in the past
<daveshah> Is this the T2 variant that is in yosys-bench?
<ZirconiumX> Yeah
<daveshah> What synth command? I think I've only tested that one with synth_xilinx
<daveshah> and that was a few months ago
<dh73> Yeah, OpenSPARC have tons of clock domains, so abc gets crazy on them. You need some modifications. I think dave did modifications once. As far as I remember, most of the crashes happened when using `-dff`
<ZirconiumX> ECP5 I think
<ZirconiumX> It takes a while to reproduce :P
nengel has quit [Ping timeout: 272 seconds]
rjo has joined #yosys
nrossi has joined #yosys
fevv8[m] has joined #yosys
promach3 has joined #yosys
jryans has joined #yosys
pepijndevos[m] has joined #yosys
fsasm has quit [Ping timeout: 272 seconds]
<GenTooMan> when is the main branch of yosys updated? When a version change occurs with a set of bug fix criteria?
<daveshah> No, almost everything goes into master
emeb_mac has joined #yosys
Thorn has joined #yosys
<GenTooMan> no tags then? Ok .. hopefully the master works then.
<daveshah> There are tags but releases are infrequent unfortunately
<daveshah> In general the releases are more buggy than master
<GenTooMan> Ok ... thanks I was wondering if I needed to update yosys as I have 0.9+932 however I haven't an idea of what (build #?) it's at
<GenTooMan> oh well execute pull and hope for the best :D
strobokopp has joined #yosys
dh73 has quit [Quit: Leaving.]
vidbina has quit [Ping timeout: 268 seconds]
likewise has quit [Remote host closed the connection]
<GenTooMan> mm not too happy having to edit yosys makefile every time I build it.
like2wise has quit [Quit: Leaving]
<ZirconiumX> GenTooMan, Makefile.conf is a thing
<ZirconiumX> You can override the Yosys Makefile rules by putting them in Makefile.conf
<GenTooMan> Well things happen this sway, yosys has a bad habit of assuming (like most applications) where you can install it. So they define the prefix wrong for the linux distribution I have. When I do a "git pull" I have to delete the Makefile so I can update the source. Makefile.conf likely is in the same category no?
<awygle> Makefile.conf isn't tracked in the repository
<awygle> so it won't have that problem
<GenTooMan> I'll check if it allows me to override PREFIX in the makefile
FL4SHK has quit [Quit: WeeChat 2.4]
FL4SHK has joined #yosys
FL4SHK has quit [Quit: rebooting]
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
<GenTooMan> it works... good to know