ChanServ changed the topic of #yosys to: Yosys Open SYnthesis Suite: https://github.com/YosysHQ/yosys/ | Channel logs: https://libera.catirclogs.org/yosys/ | Bridged to #yosys:matrix.org
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
bjorkint0sh has quit [Remote host closed the connection]
bjorkint0sh has joined #yosys
_whitelogger has joined #yosys
janrinze has quit [Ping timeout: 248 seconds]
janrinze has joined #yosys
bjorkint0sh has quit [Remote host closed the connection]
bjorkint0sh has joined #yosys
bjorkint0sh has quit [Remote host closed the connection]
bjorkint0sh has joined #yosys
bjorkint0sh has quit [Remote host closed the connection]
bjorkint0sh has joined #yosys
peeps[zen] has quit [Quit: Connection reset by peep]
peepsalot has joined #yosys
ZipCPU has quit [Ping timeout: 272 seconds]
ZipCPU has joined #yosys
FabM has joined #yosys
FabM has joined #yosys
kristianpaul has quit [Read error: Connection reset by peer]
kristianpaul has joined #yosys
postroutine has joined #yosys
<postroutine> Hello. I'm very new to Yosys and I would like to know: How it compare to HOG ?
<csantosb> This Hog ? https://gitlab.com/hog-cern/Hog
<tpb> Title: Hog / Hog · GitLab (at gitlab.com)
<postroutine> Yes.
<csantosb> I'd say they cover different goals.
<postroutine> Yes, I was confused between Yosys and the OSS-CAD-SUITE
bjorkint0sh has quit [Ping timeout: 260 seconds]
bjorkint0sh has joined #yosys
Adrien[m] has joined #yosys
<Adrien[m]> This is nextpnr with Himbaechel backen for Xilinx.
<Adrien[m]> With gdb I can get the details of the "bel" that triggers the issue :
<Adrien[m]> `bel = {tile = 15791, index = 6}`
<Adrien[m]> How can I find what type of primitive/cell this is about ?
<Adrien[m]> I think I would like to call bel_name_in_site() defined in himbaechel/uarch/xilinx/xilinx.h, but I can't figure how to call it...
<Adrien[m]> Maybe I'm supposed to call `ctx->getBelName(bel).str()` or `ctx->getBelName(bel)[0].c_str(ctx)` but these operators seem to have been optimized out during compilation...
<Adrien[m]> phew finally got it : X83Y84/SLICE_X0Y0.B6LUT
xutaxkamay has quit [Ping timeout: 248 seconds]
Ceres has joined #yosys
<Ceres> Hello, Yosys people!  Thank you for all your work on such wonderful software :)
<Ceres> I'd like to contribute some code, but I have a couple of questions...
<Ceres> (for context, I want to make "read_verilog -sv" support SystemVerilog unique/priority if, primarily by making the parser generate one big flattened AST_CASE/AST_COND.../AST_DEFAULT for "else if" branches, instead of the nested AST_CASEs it makes currently)
<Ceres> What is the best approach for submitting changes?  Should I open an enhancement issue and a pull request?  Or just pull request?  Or something else?
<Ceres> So far, I have only the syntax change implemented (i.e., the parser validates and accepts but silently ignores unique/priority if), plus documentation and test cases.  Is it better to submit this smaller change first, then work on the semantic implementation if this step is accepted?  Or is it preferable to finish all the implementation, then
<Ceres> submit an atomic PR for everything?
Ceres has quit [Quit: Client closed]
Ceres has joined #yosys
Ceres has quit [Quit: Client closed]
Ceres has joined #yosys
FabM has quit [Ping timeout: 260 seconds]
lofty[m] has joined #yosys
<lofty[m]> I would definitely break everything down into small PRs; I think most verilog frontend changes go through zachjs, so dropping a giant change on him may be too much at once.
<Ceres> Thanks, lofty!  I'll do that.
Ceres has quit [Quit: Client closed]
Ceres has joined #yosys
Ceres has quit [Quit: Client closed]
<latchflip> I'm hoping we get a CMake build of Yosys at some point.
xutaxkamay has joined #yosys
xutaxkamay has quit [Read error: Connection reset by peer]
xutaxkamay_ has joined #yosys
xutaxkamay_ is now known as xutaxkamay
nonchip has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nonchip has joined #yosys