clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
promach_ has joined #yosys
<cr1901_modern> ZipCPU: Path bug == "yosys-config returns the wrong directory on Windows." But I need to test something before actually submitting a report
seldridge has joined #yosys
<cr1901_modern> it's possible I forgot to run "make PREFIX=/path/to/root" while compiling
<ZipCPU> I just ask because Clifford and I were chasing some path bugs today.
<ZipCPU> I wasn't using Windows though
* cr1901_modern goes ahead and checks
<ZipCPU> We were looking into include paths
<ZipCPU> I was surprised to discover that yosys allows code in multiple directories, and include paths between them
<cr1901_modern> Why wouldn't it?
<ZipCPU> Exactly ... I just hadn't used that feature before.
<ZipCPU> Well, that and .... there were some bugs when using the feature with Verific ... initially, as I recall, there was no way to create new paths. Then once we fixed that, everytime you specified an include path it would get reset after a single read command.
<ZipCPU> But ... that was just my morning's work ;)
<cr1901_modern> include paths are broken on ISE too if memory serves. I.e. you can only add one
[Ristovski] is now known as Ristovski
<ZipCPU> Hmm ... I didn't check more than one
<cr1901_modern> https://github.com/YosysHQ/yosys/blob/master/Makefile#L487 (Why don't ppl use m4 for this?)
<tpb> Title: yosys/Makefile at master · YosysHQ/yosys · GitHub (at github.com)
<cr1901_modern> Yea in any case, it's my fault for not running w/ "make PREFIX="
* ZipCPU pulls up the link
<ZipCPU> With the PREFIX, does it work?
<cr1901_modern> yes. Well I haven't tested it, but I know it'll work :P
<cr1901_modern> When I see multiple sed expressions laid out like that, my first instinct is "m4 -DDATDIR=$(DATDIR)" etc
<ZipCPU> Yeah .... but I'm kind of glad it's not using m4 .... that's just one more dependency that would need to be installed to use it.
<awygle> also I'd have to learn m4 :-P
<cr1901_modern> (Tbf, POSIX requires m4 to be present :P.)
<awygle> (technically m4 would just be a build time dependency, not a runtime)
<ZipCPU> All good arguments
promach_ has quit [Quit: WeeChat 2.1]
pie___ has quit [Ping timeout: 260 seconds]
m_w has quit [Quit: Leaving]
seldridge has quit [Ping timeout: 268 seconds]
mjoldfield has quit []
mjoldfield has joined #yosys
jaafar has quit [Ping timeout: 256 seconds]
xerpi has joined #yosys
maartenBE has quit [Quit: ZNC 1.6.5+deb1 - http://znc.in]
maartenBE has joined #yosys
xerpi has quit [Quit: Leaving]
fsasm has joined #yosys
quigonjinn has quit [Remote host closed the connection]
quigonjinn has joined #yosys
knielsen has quit [Read error: Connection reset by peer]
knielsen has joined #yosys
knielsen has quit [Read error: Connection reset by peer]
knielsen has joined #yosys
keesj has quit [Quit: leaving]
cr1901_modern has quit [Read error: Connection reset by peer]
cr1901_modern has joined #yosys
fsasm has quit [Ping timeout: 248 seconds]
jwhitmore has joined #yosys
m_t has joined #yosys
jwhitmore has quit [Ping timeout: 264 seconds]
ar3itrary has quit [Read error: Connection reset by peer]
ar3itrary has joined #yosys
keesj has joined #yosys
fsasm has joined #yosys
ar3itrary has quit [Read error: Connection reset by peer]
ar3itrary has joined #yosys
X-Scale has quit [Ping timeout: 248 seconds]
dxld has quit [Quit: Bye]
dxld has joined #yosys
maikmerten has joined #yosys
fsasm has quit [Ping timeout: 240 seconds]
fsasm has joined #yosys
indy has quit [Ping timeout: 244 seconds]
promach_ has joined #yosys
pie_ has joined #yosys
seldridge has joined #yosys
indy has joined #yosys
mjoldfield has quit [Read error: Connection reset by peer]
mjoldfie_ has joined #yosys
quigonjinn has quit [Remote host closed the connection]
mjoldfie_ has quit [Read error: Connection reset by peer]
mjoldfield has joined #yosys
jwhitmore has joined #yosys
jwhitmore has quit [Ping timeout: 256 seconds]
proteus-guy has quit [Ping timeout: 260 seconds]
proteus-guy has joined #yosys
indy has quit [Quit: ZNC - http://znc.sourceforge.net]
indy has joined #yosys
m_t has quit [Quit: Leaving]
kristianpaul has quit [Quit: Lost terminal]
kristianpaul has joined #yosys
jwhitmore has joined #yosys
digshadow has quit [Ping timeout: 260 seconds]
xa0 has quit [Ping timeout: 256 seconds]
jaafar has joined #yosys
xa0 has joined #yosys
pie_ has quit [Ping timeout: 240 seconds]
xa0 has quit [Ping timeout: 244 seconds]
xa0 has joined #yosys
promach_ has quit [Quit: WeeChat 2.2]
m_w has joined #yosys
jwhitmore has quit [Ping timeout: 240 seconds]
emeb has joined #yosys
jwhitmore has joined #yosys
maikmerten has quit [Quit: Ex-Chat]
maikmerten has joined #yosys
X-Scale has joined #yosys
digshadow has joined #yosys
fsasm has quit [Ping timeout: 256 seconds]
jwhitmore has quit [Ping timeout: 256 seconds]
<maikmerten> ported my design over the the HX8K breakout board, yay! https://github.com/maikmerten/spu32/commit/5e3401f6a67064faa11896b5a037c142c72cd7bd
<tpb> Title: initial port of SoC to the Lattice HX8K breakout board · maikmerten/spu32@5e3401f · GitHub (at github.com)
<maikmerten> turns out it helps to actually double-check pin assignments and not misreading the somewhat wacky silk screen on that board
<maikmerten> in the icestorm toolchain, is there something more than toying around with the seeds to tweak timings? My design somewhat fluctuates between 45 MHz and 56 MHz depending on minor tweaks (pin assignments, minor logic tweaks far away from the critical path) so I guess "placement and routing luck" has a role here
jwhitmore has joined #yosys
<ZipCPU> maikmerten: Not sure what to say. The arachne-pnr placer isn't really timing driven, so ... it gets different timing's depending upon the random variables used to generate the placement.
<maikmerten> well, I guess that answers the question quite fine, actually ;-)
<daveshah> You can pick a seed using -s, or use -r to use a random seed each time
<daveshah> If you want to experiment without even modifying the design at all
<maikmerten> I think -r may be very useful if arachne-pnr and icetime are wrapped into a nice little script with a loop to retry if there's no timing closure
<daveshah> Because arachne-pnr is only single-threaded, it would make sense also to run 4-8 times in parallel too
<maikmerten> indeed
<daveshah> I've seen a Makefile which did this once
<tpb> Title: Makefile - talos-system-fpga - Talos™ II FPGA sources (at git.raptorcs.com)
<maikmerten> my Ryzen would sure like that
<daveshah> I would not say that Makefile is an example to follow
<maikmerten> can't be worse than mine.
<maikmerten> oh my.
<sorear> at the very least use $(seq 1 64)…
<maikmerten> yeah, -r for arachne-pnr with brute-force threading sure looks like it has very neat potential https://paste.debian.net/1034143/
<tpb> Title: debian Pastezone (at paste.debian.net)
jwhitmore has quit [Ping timeout: 260 seconds]
luismarques has quit [Quit: luismarques]
<daveshah> Haha, you could add two of the most researched and difficult parts of PnR - parallelisation and timing driven - to arachne in 10 lines of bash...
<maikmerten> of course, that would be parallelisation with no net speed gain ;-)
<awygle> but improved QoR which is still a win
<maikmerten> sure :-)
X-Scale has quit [Ping timeout: 244 seconds]
X-Scale has joined #yosys
maikmerten has quit [Quit: Ex-Chat]
seldridge has quit [Ping timeout: 240 seconds]
dxld has quit [Quit: Bye]
dxld has joined #yosys
seldridge has joined #yosys
digshadow has quit [Quit: Leaving.]
digshadow has joined #yosys
tinyfpga has quit [Ping timeout: 256 seconds]
tinyfpga has joined #yosys
digshadow has quit [Quit: Leaving.]
digshadow has joined #yosys
knielsen has quit [Read error: Connection reset by peer]
knielsen has joined #yosys
tpb has quit [Remote host closed the connection]
tpb has joined #yosys