Saturday, 2020-05-16

*** tpb has joined #yosys00:00
*** BinaryLust has joined #yosys00:11
*** mwk has quit IRC01:15
*** mwk has joined #yosys01:16
*** m_hackerfoo has quit IRC02:21
*** hackerfoo has quit IRC02:21
*** Degi has quit IRC03:22
*** Degi has joined #yosys03:23
*** oldtopman has joined #yosys05:00
*** BinaryLust has quit IRC06:28
*** dys has quit IRC06:28
*** Asu has joined #yosys07:53
*** kraiskil_ has joined #yosys08:43
sensilleis it important to do tri-stating logic only at top level? technically it shouldn't matter if the hierarchy gets flattened upfront anyway09:12
*** FFY00 has joined #yosys09:15
*** kraiskil_ has quit IRC09:30
*** kraiskil_ has joined #yosys09:45
*** vidbina has joined #yosys10:51
*** kraiskil_ has quit IRC11:18
*** vidbina has quit IRC11:21
*** kraiskil_ has joined #yosys11:21
*** Asuu has joined #yosys11:28
*** Asu has quit IRC11:28
*** gmc has quit IRC11:46
*** dys has joined #yosys11:47
*** klotz has joined #yosys11:59
*** kraiskil_ has quit IRC12:23
*** ayazar has joined #yosys12:26
*** jakobwenzel has joined #yosys13:08
*** X-Scale` has joined #yosys13:24
*** X-Scale has quit IRC13:27
*** X-Scale` is now known as X-Scale13:27
*** Asu has joined #yosys13:47
*** Asuu has quit IRC13:48
*** mirage335 has quit IRC13:49
*** mirage335 has joined #yosys13:58
tntDoes yosys have any attribute you can set to prevent it from messing / optimizing the carry chains ?14:08
tntI'm guessing it tries to optimize stuff but doing so it prevents packing and so that makes things way worse and not better.14:09
*** emeb has joined #yosys14:09
ZirconiumXMaybe a (* keep *)?14:25
ZirconiumXI mean, carry chains are whiteboxes14:25
ZirconiumXSo only ABC9 can really "optimise" them14:25
tntWith abc9 the bottom lut ends up with the inputs not on the right ports for packing. Without it (so "old" abc), then the top luts end up with the input on the wrong ports for packing.14:26
tnt(because really it doesn't end up actually using any less luts or anything, just not using the right lut inputs for packing)14:27
ZirconiumXThat...seems like a nextpnr thing?14:28
tntnextpnr expects some specific lut input to be common to the SB_LUT4 and the SB_CARRY for them to be packable in the same LC.14:29
*** gmc has joined #yosys14:51
*** jakobwenzel1 has joined #yosys14:57
tntMmm, my understanding was that it was using \$__ICE40_CARRY_WRAPPER to avoid that kind of issue.14:59
*** klotz has quit IRC15:02
*** jakobwenzel1 has quit IRC15:24
*** gmc has quit IRC15:29
*** BinaryLust has joined #yosys15:38
*** citypw has joined #yosys15:47
*** gmc has joined #yosys15:52
*** gmc has quit IRC15:59
*** gmc has joined #yosys16:13
*** vidbina has joined #yosys16:17
*** bzztploink has joined #yosys16:23
tntSo the issue is the opt_lut pass16:50
tntMm ... yeah, I see the " -dlogic SB_CARRY:I0=2:I1=1:CI=0" which I assume is to prevent it from messing with I1/I2 that must stay in place for the SB_CARRY to stay there.17:02
tntBut there is nothing that prevents it from moving the signal coming from a SB_CARRY to I3 to somewhere else.17:02
ZirconiumXFile a bug if you haven't already17:11
whitequarktnt: oh ugh I missed that17:12
whitequarkopt_lut keeps being a PITA17:13
tntI'm collecting info and trying to make the absolute minimum case.17:13
tnthttps://github.com/YosysHQ/yosys/issues/206117:30
tpbTitle: ice40: opt_lut can break carry packing by moving SB_CARRY out to another input than I3 · Issue #2061 · YosysHQ/yosys · GitHub (at github.com)17:30
*** gmc has quit IRC17:48
*** citypw has quit IRC17:51
*** klotz has joined #yosys18:02
*** BinaryLust has quit IRC18:21
*** klotz has quit IRC18:27
*** dys has quit IRC18:31
*** rlee287 has joined #yosys18:43
*** DaKnig has quit IRC18:48
*** DaKnig has joined #yosys18:50
*** vidbina has quit IRC19:23
*** rlee287 has quit IRC20:07
*** rlee287 has joined #yosys20:08
*** rlee287 has quit IRC20:20
*** adjtm_ has joined #yosys20:27
*** adjtm has quit IRC20:29
*** ayazar has quit IRC20:34
*** vidbina has joined #yosys20:52
*** DaKnig has quit IRC21:02
*** DaKnig has joined #yosys21:02
*** BinaryLust has joined #yosys21:22
*** vidbina has quit IRC22:03
*** dys has joined #yosys22:03
*** Asu has quit IRC22:12
*** az0re has quit IRC22:13
Forty-Botis it possible to access module parameters from another module?22:17
Forty-Bote.g. something like https://gist.github.com/Forty-Bot/d16632f50085ce708ad915a2d263a29322:17
tpbTitle: gist:d16632f50085ce708ad915a2d263a293 · GitHub (at gist.github.com)22:17
ZirconiumXNo22:34
ZirconiumXBut in your case, you don't need to22:35
Forty-Botwell, yeah22:35
Forty-Botbut the actual case I am concerned about22:35
Forty-BotFOO and BAR have non-trivial formulae22:35
ZirconiumXCan they be computed as constant expressions?22:35
Forty-Botprobably?22:36
ZirconiumX"can you instantiate a wire that is PARAM bits wide?"22:36
Forty-Botthat is what I would like to do22:36
ZirconiumXYou can use `localparam` to create a compile-time constant22:39
*** cr1901_modern has quit IRC23:39
*** cr1901_modern has joined #yosys23:41
*** rlee287 has joined #yosys23:51
*** emeb has left #yosys23:51
*** bzztploink has quit IRC23:57

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!