Tuesday, 2018-03-20

*** tpb has joined #vtr-dev00:00
*** digshadow has quit IRC02:35
*** digshadow has joined #vtr-dev04:58
*** digshadow has quit IRC17:01
*** digshadow has joined #vtr-dev17:33
mithrokem_: I think I've found a weird bug in the rr_graph generation stuff - trying to produce a minimal test case to understand what is going on19:15
tpbTitle: Snippet | IRCCloud (at www.irccloud.com)19:16
mithroIt very much looks like the edges are getting connected to the wrong nodes -- I'm seeing the same thing in the rr_graph.echo file...19:38
kem_Getting to a MWE is the right approach20:27
kem_I assume this is for an RR graph that VPR built?20:27
mithrokem_: Yeah20:39
mithrokem_: I'm trying to make sure I just haven't done something really stupid in my architecture file20:39
mithrokem_: I have been working on a Python library for manipulating rr_graphs20:41
kem_mithro: Makes a lot of sense!20:42
mithrokem_: If you want a distraction, I could explain how to build my architecture files20:44
kem_mithro: Perhaps not at the moment, but definitely in the future! Last time I looked at one it was somewhat difficult to follow, so understanding how they are put together would likely help :)20:48
mithrokem_: Sure, I have a bunch of much simpler "test" architectures now20:49
mithrokem_: Welp - hit a different bug now...21:50
mithrokem_: https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/31021:50
tpbTitle: Segfault in alloc_and_load_track_top_pin_lookup · Issue #310 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)21:50

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