Tuesday, 2020-01-14

*** tpb has joined #yosys00:00
*** emeb has quit IRC00:31
*** tlwoerner has quit IRC05:51
*** rohitksingh has joined #yosys05:52
*** craigo has joined #yosys05:52
*** tlwoerner has joined #yosys06:29
*** emeb_mac has quit IRC06:58
*** citypw has joined #yosys06:58
*** fsasm has joined #yosys07:02
*** citypw has quit IRC07:08
*** rohitksingh has quit IRC07:25
*** dys has joined #yosys09:11
*** vidbina_ has joined #yosys09:31
*** vidbina_ has quit IRC10:02
*** vidbina_ has joined #yosys10:04
*** fsasm has quit IRC10:12
*** fsasm has joined #yosys10:20
*** vidbina_ has quit IRC11:27
*** az0re has joined #yosys11:40
*** GenTooMan has quit IRC11:47
*** GenTooMan has joined #yosys11:48
*** fsasm has quit IRC12:06
*** az0re has quit IRC12:08
*** GenTooMan has quit IRC12:37
*** craigo has quit IRC13:13
*** craigo has joined #yosys13:13
*** dh73 has joined #yosys13:23
*** dh73 has quit IRC14:04
*** X-Scale` has joined #yosys14:06
*** X-Scale has quit IRC14:08
*** X-Scale` is now known as X-Scale14:08
*** attie has joined #yosys14:50
*** emeb has joined #yosys15:44
*** dh73 has joined #yosys16:01
*** GenTooMan has joined #yosys16:08
*** jakobwenzel has quit IRC16:30
*** captain_morgan20 has quit IRC16:39
*** alexhw has quit IRC17:10
*** alexhw has joined #yosys17:12
*** alexhw has quit IRC17:14
*** alexhw has joined #yosys17:25
*** alexhw has quit IRC17:27
*** dys has quit IRC17:35
*** Jybz has joined #yosys17:43
*** craigo has quit IRC17:56
*** attie has quit IRC18:13
*** emeb has left #yosys18:25
*** Jybz has quit IRC18:26
*** alexhw has joined #yosys18:44
ZirconiumXWelp; I found another Yosys bug18:46
ZirconiumXBut it seems to be an infinite loop?18:46
*** attie has joined #yosys19:15
ZipCPUReally?19:20
ZirconiumXZipCPU: https://github.com/YosysHQ/yosys/issues/1634 <-- not an infinite loop, but unreasonably high19:24
tpbTitle: fsm_detect takes a very long time · Issue #1634 · YosysHQ/yosys · GitHub (at github.com)19:24
*** indy has quit IRC19:26
*** X-Scale` has joined #yosys19:45
*** X-Scale has quit IRC19:48
*** X-Scale` is now known as X-Scale19:48
*** attie has quit IRC19:51
*** az0re has joined #yosys19:53
*** attie has joined #yosys20:03
*** indy has joined #yosys20:14
ZipCPUZirconiumX: Which block is the one giving you the problem?20:28
ZirconiumXZipCPU: "which block"? What do you mean by "block" here?20:29
ZipCPUalways20:29
ZirconiumXZipCPU: I'm working in nMigen, so there's no direct correlation as such20:31
ZipCPUSo ... this isn't the Yosys input?20:31
ZirconiumXIt is the Yosys input20:32
ZipCPUSo then one of the always blocks must be the one giving yosys the hassle20:32
ZirconiumXYes, but I don't know which and Yosys does not have the functionality to diagnose the issue by itself at present20:33
whitequarkalways blocks in verilog correspond to processes in nmigen-generated rtlil20:33
ZipCPUBisect the code then?20:33
whitequarkor you could also use nmigen to write verilog20:34
whitequarkalso that20:34
daveshahwhat about bugpoint -yosys <script containing timeout 10 yosys>20:34
ZipCPUdaveshah: Is there any documentation on how to use that?20:34
daveshahhelp bugpoint20:35
daveshah"-yosys" is intended to use an alternative Yosys binary20:35
daveshahbut I think timeout should work here too20:35
daveshah*a shell script containing timeout20:35
ZirconiumXFortunately the bug is reproducible with my current nMigen code20:35
ZirconiumXGiven the warning, I think it's a misrecognised FSM register20:36
ZirconiumXEven so, it should not take five and a half minutes20:36
ZipCPUAbsolutely!20:36
ZipCPUThe question is how to narrow the problem down sufficiently to find the root cause20:36
ZipCPUNot whether or not there's a problem20:36
ZirconiumXdaveshah: Hmm, I'd need to combine it with -grep or else any Yosys error counts as a "crash"20:41
ZirconiumXBut I don't see a way to get `timeout` to do that20:41
ZirconiumXEither way, there are only about 54 lines in the output verilog between "working" and "broken"20:43
whitequarkyou can make a shell conditional20:44
whitequarkalong the lines of `if timeout yosys`20:44
ZirconiumXRight, think I've got it20:53
*** attie has quit IRC20:57
ZirconiumXSo, I'm noticing that nextpnr's SA seems to produce higher but less-consistent Fmax values than HeAP. Is this expected?21:20
daveshahSlightly higher is definitely possible on some designs21:22
daveshahless-consistent is probably just down to the more random nature of Sa21:22
ZirconiumXWell, this design is kind of artificial, but HeAP seems to max out at 300MHz or so, and SA just gave me a 438 MHz solution21:22
ZirconiumX(ECP5)21:22
daveshahOh, do you have any IO constraints?21:23
ZirconiumXAt present no21:23
daveshahAs it stands to avoid a singular matrix HeAP randomly constrains unconstrained IO at the start, whereas SA optimises IO21:23
daveshahI haven't done a nicer solution as 99.9% of real world designs have constrained IO21:24
ZirconiumXAh, fair enough21:24
*** fsasm has joined #yosys21:38
*** fsasm has quit IRC23:05
*** emeb has joined #yosys23:23
*** TheHolyC has quit IRC23:50
*** TheHolyC has joined #yosys23:50

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!