| *** tpb has joined #symbiflow | 00:00 | |
| *** kraiskil has joined #symbiflow | 00:34 | |
| *** kraiskil has quit IRC | 00:39 | |
| *** citypw has joined #symbiflow | 03:11 | |
| *** Bertl is now known as Bertl_zZ | 04:11 | |
| *** kraiskil has joined #symbiflow | 07:45 | |
| *** kraiskil has quit IRC | 07:49 | |
| *** kraiskil has joined #symbiflow | 08:01 | |
| *** citypw has quit IRC | 09:15 | |
| *** aurodas has joined #symbiflow | 09:45 | |
| aurodas | hello! | 09:45 |
|---|---|---|
| aurodas | I am a student looking to participate in GSoC this year | 09:46 |
| aurodas | I have worked with FPGAs and I know Verilog & SystemVerilog | 09:47 |
| aurodas | are there other project ideas possible for GSoC other than the issues list specified? | 09:48 |
| *** kraiskil has quit IRC | 10:01 | |
| *** kraiskil has joined #symbiflow | 10:17 | |
| *** OmniMancer has joined #symbiflow | 11:08 | |
| *** kraiskil has quit IRC | 12:08 | |
| *** Bertl_zZ is now known as Bertl | 14:01 | |
| *** OmniMancer has quit IRC | 14:26 | |
| *** citypw has joined #symbiflow | 14:33 | |
| *** sxpert has quit IRC | 15:23 | |
| *** aurodas has quit IRC | 15:23 | |
| *** sxpert has joined #symbiflow | 15:26 | |
| litghost | aurodas: What is your interest area? We have work at all levels of the tool chain | 15:28 |
| *** citypw has quit IRC | 15:41 | |
| sf-slack1 | <acomodi> modes issue update: I am currently dealing with the creation of a VPR test to target the changes of https://github.com/SymbiFlow/vtr-verilog-to-routing/pull/29. I have added a regression test in `vtr/vtr_flow/tasks/regression_tests/vtr_reg_strong/` alongside with a small test architecture in `vtr/vtr_flow/arch/` and the .eblif file. I still couldn't get to reproduce the issue with the small test architecture | 16:58 |
| tpb | Title: Sign in to GitHub · GitHub (at github.com) | 16:58 |
| sf-slack1 | <acomodi> litghost: this was the idea, right? I will push the test in a bit, which is not yet working as expected though, but it can give an idea if the direction is the correct one | 17:00 |
| litghost | acomodi: Yes, that was the idea. | 17:00 |
| sf-slack1 | <acomodi> here's the commit relative to the initial work on the regression test https://github.com/SymbiFlow/vtr-verilog-to-routing/pull/29/commits/3ec13e42bd492e1d8d12ab0a14f6a5b66b2a9e33 | 17:12 |
| tpb | Title: WIP: Differing modes between lib_nets fix by acomodi · Pull Request #29 · SymbiFlow/vtr-verilog-to-routing · GitHub (at github.com) | 17:12 |
| litghost | acomodi: But if I understood your earlier message, that test case does not fail in the absence of #29? | 17:14 |
| sf-slack1 | <acomodi> No, the test case is still conceptually wrong, I am trying to simulate the situation for which I have a mode conflict that should be solved with #29 | 17:15 |
| litghost | acomodi: Can you start with the xc7 arch, and whittle it down? | 17:17 |
| sf-slack1 | <acomodi> litghost: I still have to modify the test architecture to get to a situation for which there are a series of siblings pb_types which have the same parent, but they are using different `modes` | 17:17 |
| sf-slack1 | <acomodi> litghost: Sounds good, I have been trying to generate an architecture from scratch, but probably the best way is actually to shrink the xc7 arch | 17:18 |
| sf-slack1 | <acomodi> litghost: The only thing then would be to produce a .blif file compatible with the architecture, which should be manually produced, right? | 17:19 |
| litghost | acomodi: I would start with your blif, whittle the arch down, then whittle the blif down | 17:20 |
| sf-slack1 | <acomodi> litghost: sounds good, thanks | 17:21 |
| sf-slack1 | <tmichalak> update on the stabilization of the CI runs: they are still giving me a headache as they are not reproducible locally. However, I try to take one step at a time and solve other issues that are related to this topic, such as https://github.com/SymbiFlow/prjxray/issues/714 . I added a waiver to the DRC rules that caused the 056-pip-rem fuzzer to fail and opened a PR https://github.com/SymbiFlow/prjxray/pull/728 just | 18:53 |
| sf-slack1 | for the purpose of running the CI. The first CI run passed for this PR, but this might just be pure luck. | 18:53 |
| tpb | Title: Make the pip fuzzers able to handle DRC check failures · Issue #714 · SymbiFlow/prjxray · GitHub (at github.com) | 18:53 |
| sf-slack1 | <tmichalak> @litghost: I saw you and mithro use a kokoro:force-run tag here and there. Is that a better way of rerunning the CI build that pushing a bogus commit to the repo? | 18:55 |
| litghost | tmichalak: Ya | 18:56 |
| sf-slack1 | <tmichalak> @litghost: is that a label that anyone can add or is it restricted to some users? | 18:57 |
| litghost | tmichalak: Unclear, but I expect anyone can use it | 19:01 |
| sf-slack1 | <tmichalak> @mithro: I also wanted to look into https://github.com/SymbiFlow/prjxray/issues/713, however not all items on the todo list are clear to me. Actually, I left my comments in the ticket. Could you elaborate on those points? | 19:02 |
| tpb | Title: Issues · SymbiFlow/prjxray · GitHub (at github.com) | 19:02 |
| sf-slack1 | <tmichalak> @mithro: do you think that PR https://github.com/SymbiFlow/prjxray/pull/712 can be merged? I get to see a lot of these "jobserver unavailable" warning messages in the logs. | 19:04 |
| tpb | Title: Fix makefiles to pass -j option by tmichalak · Pull Request #712 · SymbiFlow/prjxray · GitHub (at github.com) | 19:04 |
| *** vzcx has joined #symbiflow | 20:31 | |
| *** vzcx has quit IRC | 21:15 | |
| elms | litghost: What do you think the right path is for graph/graph2 channel/channel2 stuff? Do you is would be best to just rewrite the ice40 routing import using graph2 (and possibly the database cache)? then we can just surplant graph.py? | 22:45 |
| elms | If so I think we need to build out testing and docstrings significantly in the new (2) approach. | 22:46 |
| litghost | elms: I don't think a move to include the database cache is required. The observation I made during the xc7 routing import was that most of graph/channel were a distraction from what was actually required for routing import. The only thing that is really necessarily is channel formation, IPIN/OPIN lookup and serialization. Everything else was/is superfluous. | 22:48 |
| litghost | elms: In terms of what I think should be done for the ice40 routing import, I think the first step is to refactor the import to avoid the majority of either graph or graph2, as most of it's functionality is purely about the routing graph. If we wanted to refactor that to use the sqlite format, okay, but I don't think that is strictly speaking required. | 22:49 |
| litghost | elms: In general, graph2 and channel2 are dramatic simplifications of graph and channel, burning away the unneeded parts. | 22:49 |
| litghost | elms: I do not recommend we rebuild the complexity present in the old libraries, that complexity was never required | 22:50 |
| elms | litghost: not sure I follow. I'll have to look closer at graph2 to see what graph has and you are saying are not required. Do you recall examples of some unneeded things? | 22:51 |
| litghost | elms: Concrete example, modeling of BlockTypes. https://github.com/SymbiFlow/symbiflow-arch-defs/blob/master/utils/lib/rr_graph/graph.py#L631-L907 | 22:52 |
| tpb | Title: symbiflow-arch-defs/graph.py at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com) | 22:52 |
| litghost | elms: All 300 lines of that code is not required at all | 22:52 |
| litghost | elms: The entire portion of graph2 related to BlockTypes and the grid can be found https://github.com/SymbiFlow/symbiflow-arch-defs/blob/master/utils/lib/rr_graph/graph2.py#L119-L181 and https://github.com/SymbiFlow/symbiflow-arch-defs/blob/master/utils/lib/rr_graph_xml/graph2.py#L100-L240 | 22:55 |
| tpb | Title: symbiflow-arch-defs/graph2.py at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com) | 22:55 |
| litghost | elms: All that code is doing is providing IPIN/OPIN to node lookup | 22:55 |
| litghost | elms: Which is pretty much all that is required. | 22:55 |
| elms | ok. I'm in the ice40 routing import to remove HLC anyway. I'll look at reducing the some of that at the same time. | 22:56 |
| elms | litghost: I think using the databasecache may be good just to keep structure similar across archs. It will hopefully make it easier for new archs if we can keep them closer than we have in the past. | 22:58 |
| litghost | elms: I don't disagree, I just want to be clear that graph vs graph2 is orthogal to using the database | 22:58 |
| elms | litsghost: yep, understood | 22:59 |
| litghost | elms: I think the simplest way to understand the difference between graph and graph2 is the number of methods. | 23:05 |
| litghost | graph.py => 88 methods | 23:05 |
| litghost | channel.py => 43 methods | 23:05 |
| litghost | graph2.py => 12 methods | 23:05 |
| litghost | channel2.py => 3 methods | 23:05 |
| litghost | elms: And I would claim the graph2/channel2 provides what is required to support routing import (as demostrated by the xc7 routing import). | 23:06 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!