<so-offish>
Is TRELLIS_SLICE no longer supported in nextpnr?
<tnt>
No, AFAIK it got split.
<so-offish>
Yeah it looks like it got split but it's listed as a supported primitive (also Yosys will merrily still spit out TRELLIS_SLICE as a valid techlib cell)
datenwolf has joined #yosys
<datenwolf>
Hi, everone. If I intended to hack on the nextpnr GUI, which would be the most sensible tag/commit to start from right now?
<tnt>
so-offish: When does yosys emit it ?
<tnt>
so-offish: you mean if you instanciate it ? Well yeah, I think it'll be happy to emit whatever. It's still in the sim models to allow sim of old stuff but it shouldn't emit any by itself.
<so-offish>
tnt: You're right, it's instantiated. I see what you mean: It won't take some set of combinatorial and clock logic and use a TRELLIS_SLICE for this.
<lofty>
so-offish: split slice has a lot of technical advantages, which is why it was done. the downside is that manual instantiation of TRELLIS_SLICE broke
gdd has quit [Ping timeout: 260 seconds]
bjorkint0sh has joined #yosys
gdd has joined #yosys
datenwo1f has joined #yosys
datenwolf has left #yosys [#yosys]
datenwo1f is now known as datenwolf
datenwolf has quit [Quit: WeeChat 3.8]
datenwolf has joined #yosys
<lofty>
datenwolf: I don't think the GUI stuff is touched much, so it shouldn't matter, but I would still follow git master in this case
<datenwolf>
thanks. Mostly I want to go after Qt complaining about an unhandled exception reaching its signals/slots system.
<datenwolf>
and by that I mean: Figure out what's throwing that exception, figure out why it's called in a UI context, address that, and then fix whatever is causing that exception in the first place
bjorkint0sh has quit [Quit: Leaving]
DiffieHellman has quit [Remote host closed the connection]