clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
emeb_mac has joined #yosys
emeb has quit [Quit: Leaving.]
josi has quit [Ping timeout: 246 seconds]
josi has joined #yosys
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
Degi has quit [Ping timeout: 240 seconds]
Degi has joined #yosys
futarisIRCcloud has joined #yosys
citypw has joined #yosys
<ross_s> Following up on earlier, I had some time to put together a small tool for exploring resource usage based on the output from yosys. All source code is here if anyone is interested: https://github.com/rschlaikjer/yostat
<ross_s> If anyone knows a good way to detect which cells are 'primitives' from the JSON, that would be good to know - currently I just have a list of ECP5 cells
<whitequark> you basically have to know it upfront
<whitequark> but you can approximate it very well by looking for the blackbox attribute
<whitequark> (it's possible that people will add custom blackboxes but it's rare)
<ross_s> hmm, yeah that looks like it'll work
<ross_s> will probably patch that in tomorrow
<az0re> whitequark: Can you remind me of the exact format of hdlname?
<az0re> And it's just an attribute for wires, right?
emeb_mac has quit [Quit: Leaving.]
indy has quit [Ping timeout: 265 seconds]
indy has joined #yosys
<whitequark> az0re: the manual has it; the format is a sequence of public names separated by a single space
<az0re> I need to think if that can be used instead of source location, and if there is a benefit to doing it that way
<az0re> There is already an attempted name match
<whitequark> there's one more aspect, which is that a single logical wire can be composed of multiple wires with the same hdlname but nonoverlapping offset/size
<az0re> Right
<az0re> I'm not sure that matters, though, as the matching is done SigBit-by-SigBit
kgugala has quit [Ping timeout: 258 seconds]
jakobwenzel has joined #yosys
gmc has joined #yosys
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
Asu has joined #yosys
jeanthom has joined #yosys
adjtm_ has quit [Ping timeout: 260 seconds]
Sarayan has quit [Quit: rewbooting]
adjtm has joined #yosys
acomodi has joined #yosys
<acomodi> Hi all, I have a question on verilog attributes. I was using a ~7 months old yosys version, and, upon using the current master, the LOC constraints on primitives of the verilog design stopped to end up in the generated eblif. Has the way of handling attributes changed in these months?
<Lofty> "LOC constraints on primitives of the verilog design"?
<acomodi> (* LOC="SLICEXY" *)
<Lofty> Perhaps you could try a git bisect
<daveshah> Also, use ilang to see if the attributes exist at various points in the flow
<daveshah> in particular, whether they are being dropped at the frontend, during flattening or in the bleif backend
<acomodi> Ok, I'll check that, thanks
jfcaron has joined #yosys
proteusguy has quit [Ping timeout: 256 seconds]
indy has quit [Read error: Connection reset by peer]
X-Scale` has joined #yosys
X-Scale has quit [Ping timeout: 264 seconds]
X-Scale` is now known as X-Scale
indy has joined #yosys
proteusguy has joined #yosys
jeanthom has quit [Ping timeout: 264 seconds]
<acomodi> The attribute absence issue seem to be related to abc9. For instance, when running synth_xilinx without abc9, the LOC attribute does not get dropped, while when enabling abc9, the attribute gets dropped.
<acomodi> Here's a reduced form of the design: https://we.tl/t-2ziEJMdneo. I tested it on the following yosys version: Yosys 0.9+2406 (git sha1 ede4b10d, clang 6.0.0-1ubuntu2 -fPIC -Os). the run.sh script synthesize without abc9, while the run_abc9.sh enables abc.
<daveshah> Probably what changed is that flops are now being passed through abc9 to some extent, and the various mappings/unmappings end up losing attributes
<daveshah> This should definitely be fixed though, as constrained FFs are useful for many a reason
<acomodi> All right, should I open an issue with the failing test and a brief on GH?
<acomodi> brief explanation*
<daveshah> Yes please, I haven't followed abc9 developments that closely recently so I'm not the best person to fix it
jeanthom has joined #yosys
Cerpin has joined #yosys
kraiskil has joined #yosys
<jeanthom> Hi, I'm running into a "DQS group mismatch" error when trying to compile a DDR3 design (the full error message is "ERROR: DQS group mismatch, port DQSW270 of 'ddrphy.U$$25' in group LDQ41 is driven by DQSBUFM 'ddrphy.U$$26' in group LDQ77"). I was wondering if it's a bug from nextpnr or if it could be something wrong/missing in my HDL code?
<daveshah> Does the design build in Diamond?
kraiskil_ has joined #yosys
<daveshah> Have you compared the message with the DQS groups (in the pinout file)?
kraiskil_ has quit [Read error: Connection reset by peer]
kraiskil has quit [Ping timeout: 264 seconds]
josi has quit [*.net *.split]
daknig has quit [*.net *.split]
pepijndevos has quit [*.net *.split]
promach3 has quit [*.net *.split]
jhol has quit [*.net *.split]
filt3r has quit [*.net *.split]
citypw has quit [*.net *.split]
az0re has quit [*.net *.split]
jryans has quit [*.net *.split]
kraiskil_ has joined #yosys
josi has joined #yosys
citypw has joined #yosys
daknig has joined #yosys
filt3r has joined #yosys
jhol has joined #yosys
pepijndevos has joined #yosys
az0re has joined #yosys
jryans has joined #yosys
jryans has quit [Max SendQ exceeded]
futarisIRCcloud has joined #yosys
futarisIRCcloud has quit [Changing host]
futarisIRCcloud has joined #yosys
madushan1000 has quit [Ping timeout: 240 seconds]
fevv8[m] has quit [Ping timeout: 244 seconds]
emily has quit [Ping timeout: 260 seconds]
citypw has quit [Ping timeout: 240 seconds]
kraiskil_ has quit [Read error: Connection reset by peer]
jakobwenzel has quit [Remote host closed the connection]
<az0re> whitequark: if you rename() a wire or cell in a design, does that update the `hdlname` attribute?
<az0re> Or does that AttrObject retain its original `hdlname` attribute?
X-Scale has quit [Ping timeout: 260 seconds]
emeb has joined #yosys
nurelin has joined #yosys
X-Scale has joined #yosys
acomodi has quit [Quit: Connection closed for inactivity]
<mwk> az0re: it's untouched; how would it even work if you wanted to update it?
<az0re> Right, just making sure
az0re has quit [Remote host closed the connection]
Nazara has quit [Ping timeout: 246 seconds]
Nazara has joined #yosys
az0re has joined #yosys
Nazara has quit [Ping timeout: 264 seconds]
Nazara has joined #yosys
Nazara_ has joined #yosys
Nazara has quit [Ping timeout: 265 seconds]
Nazara_ is now known as Nazara
kraiskil_ has joined #yosys
philtor has joined #yosys
jfcaron has quit [Ping timeout: 260 seconds]
az0re has quit [Ping timeout: 240 seconds]
Asu has quit [Ping timeout: 246 seconds]
Asuu has joined #yosys
az0re has joined #yosys
jeanthom has quit [Ping timeout: 260 seconds]
az0re has quit [Ping timeout: 240 seconds]
az0re has joined #yosys
Asuu has quit [Remote host closed the connection]
emeb has quit [Quit: Leaving.]
mwk has quit [Ping timeout: 264 seconds]
emeb_mac has joined #yosys
mwk has joined #yosys
awordnot has quit [Read error: Connection reset by peer]
awordnot has joined #yosys