Sunday, 2019-03-24

*** tpb has joined #symbiflow00:00
duck2hello00:28
duck2i made an incremental reader with libxml++ which can load rr_graph_xc7a50t_test.rr_graph.real.xml into a rrgraph-like struct00:30
duck2there are a few problems though00:32
duck2a) i saw ~800M of memory allocated for the struct, but the file itself is 990M. it also takes a long time: ~20 mins on my laptop with -O300:37
duck2b) libxml++ is awkward. i couldn't get my code to compile without using pkg-config which outputs 3 lines of include directories. there is also no dbg package for debian testing so i cannot profile it either.00:53
duck2for b) i think i will use plain libxml2 which is cmake friendly, uses byte arrays(not Glib::ustrings) and has a debug package. hopefully that will solve a). /update01:10
litghostduck2: That seems like a lot of memory.  Are you using packed structures?01:10
duck2not currently. i think the bulk of the memory comes from edges which all have a single-element vector of metadata attached to them. i wonder how flatbuffers handles this.01:18
*** OmniMancer has joined #symbiflow01:23
*** futarisIRCcloud has joined #symbiflow04:24
*** _whitelogger has quit IRC04:28
*** _whitelogger has joined #symbiflow04:31
*** Bertl is now known as Bertl_zZ05:43
*** futarisIRCcloud has quit IRC06:44
*** futarisIRCcloud has joined #symbiflow07:36
*** futarisIRCcloud has quit IRC09:44
*** i8hantanu has joined #symbiflow09:45
*** tmichalak has quit IRC10:56
*** futarisIRCcloud has joined #symbiflow11:06
*** Mr has joined #symbiflow11:53
Mrwhat should i do11:54
MrHello11:55
sf-slack1<tmichalak> Mr: Hi, there are plenty of things you can do, depends on your skills or what you want to work on. Have a look at the issues in all symbiflow repositories and for starters look for issues tagged with `help wanted` and `good first issue`. For example here: https://github.com/SymbiFlow/prjxray/labels/help%20wanted12:47
tpbTitle: Issues · SymbiFlow/prjxray · GitHub (at github.com)12:47
*** futarisIRCcloud has quit IRC13:25
*** Mr has quit IRC13:31
*** kraiskil has joined #symbiflow13:44
*** OmniMancer has quit IRC15:09
*** kraiskil has quit IRC15:20
*** kraiskil has joined #symbiflow15:36
*** kraiskil has quit IRC15:42
*** kraiskil has joined #symbiflow15:46
*** kraiskil has quit IRC15:54
*** Bertl_zZ is now known as Bertl16:51
*** kraiskil has joined #symbiflow20:02
*** sorear has quit IRC20:27
*** sorear has joined #symbiflow20:27
duck2litghost: i brought it down to 500M and ~40 secs. now i think you were right about reading directly into device_ctx. if edges indeed appear after nodes and switches, they all can be read in right off(no need for intermediate struct). the other rr_graph structures are so small that it takes effectively no memory to cache them(grid, segments, block_t21:33
duck2ypes...)21:33
duck2here is the standalone reader i've been working on: https://gist.github.com/duck2/02d001727a252de4a118ae63b680a11c21:36
tpbTitle: draft for rr_graph.xml reader with SAX · GitHub (at gist.github.com)21:36
*** kraiskil has quit IRC21:49

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