clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
smkz has quit [Quit: smkz]
smkz has joined #yosys
smkz has quit [Client Quit]
smkz has joined #yosys
citypw has joined #yosys
citypw has quit [Client Quit]
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #yosys
citypw has joined #yosys
gorbak25 has quit [Ping timeout: 240 seconds]
gorbak25 has joined #yosys
az0re has joined #yosys
<knielsen> set subblocks [get_designs -quiet $CHIPSTRUCTURE(HIERARCHY,$PD_block,HIER)]
<knielsen> oops, sorry :-/
<az0re> Does anyone have experience with PerformanceTimer ? I'm trying to use it in a very simple way but it's giving me erroneous timing info. 3m40s of wall clock time is reported as 0.05s
<az0re> (asking again)
proteusguy has quit [Quit: Leaving]
<whitequark> which OS?
<whitequark> hm
proteusguy has joined #yosys
<whitequark> looking at log.h, PerformanceTimer only measures self time
<whitequark> so if you're running an external process that is slow, it won't be counted
dys has joined #yosys
pacak has joined #yosys
craigo has quit [Ping timeout: 246 seconds]
emeb_mac has quit [Quit: Leaving.]
<az0re> It subtracts time spent in a child process?
<az0re> I must have missed that
<az0re> Thanks
<az0re> Any idea how to get it not to do that?
<whitequark> it doesn't subtract it
<whitequark> it doesn't measure it
<whitequark> it uses the performance counters for this process only
<whitequark> try replacing RUSAGE_SELF with RUSAGE_CHILDREN
az0re has quit [Ping timeout: 240 seconds]
kraiskil has joined #yosys
Asu has joined #yosys
Cerpin has quit [Ping timeout: 258 seconds]
Cerpin has joined #yosys
jakobwenzel has joined #yosys
vidbina has joined #yosys
craigo has joined #yosys
mirage335 has quit [Ping timeout: 246 seconds]
mirage335 has joined #yosys
jfcaron_ has joined #yosys
emeb has joined #yosys
kraiskil has quit [Ping timeout: 265 seconds]
kraiskil has joined #yosys
develonepi3 has joined #yosys
X-Scale` has joined #yosys
vidbina has quit [Ping timeout: 265 seconds]
X-Scale has quit [Ping timeout: 265 seconds]
X-Scale` is now known as X-Scale
jfcaron_ has quit [Remote host closed the connection]
SpaceCoaster has quit [Quit: ZNC 1.6.5+deb1+deb9u2 - http://znc.in]
jfcaron has joined #yosys
SpaceCoaster has joined #yosys
dys has quit [Ping timeout: 260 seconds]
citypw has quit [Ping timeout: 240 seconds]
alexhw has joined #yosys
jmamish has joined #yosys
jmamish has quit [Ping timeout: 260 seconds]
jakobwenzel has quit [Quit: jakobwenzel]
az0re has joined #yosys
<az0re> whitequark: Thanks a lot :)
<whitequark> np
dys has joined #yosys
rlee287 has joined #yosys
kraiskil has quit [Ping timeout: 260 seconds]
kraiskil has joined #yosys
craigo has quit [Ping timeout: 260 seconds]
kraiskil has quit [Ping timeout: 246 seconds]
jfcaron has quit [Ping timeout: 246 seconds]
Asu has quit [Ping timeout: 256 seconds]
mwk has quit [Ping timeout: 272 seconds]
<rlee287> What does the $slice cell do? From the Verilog backend I would guess that it selects some bits from a bitvector, but the manual has a "FIXME" stating that it needs to be documented. Is there some other place where I can look for more information?
BinaryLust has joined #yosys
adjtm_ has joined #yosys
adjtm has quit [Ping timeout: 256 seconds]
<Lofty> whitequark probably knows, but I believe you are correct; it's a partial selection of a net
X-Scale` has joined #yosys
X-Scale has quit [Ping timeout: 258 seconds]
X-Scale` is now known as X-Scale