Wednesday, 2019-03-06

*** tpb has joined #vtr-dev00:00
litghostkem_: https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/47900:03
tpbTitle: High fanout routing logic causes routing failure · Issue #479 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)00:03
litghostSome of the routing checks have to be disabled, hence https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/47800:03
tpbTitle: WIP: Replicate fan out issue by litghost · Pull Request #478 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)00:04
litghosthttps://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/478 also contains https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/473 because the arch and rrgraph have metdata00:04
tpbTitle: WIP: Replicate fan out issue by litghost · Pull Request #478 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)00:04
*** digshadow has left #vtr-dev04:23
litghostkem_:  Have you had a chance to look at https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/473  ?17:27
tpbTitle: Add metadata support to architecture and rr_graph XML. by litghost · Pull Request #473 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)17:27
kem_litghost: I had a quick browse through it, but haven't had time to write up a review in detail... hopefully in the next couple of days17:53
litghostkem_: Thanks!17:53
litghostkem_: We found https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/485 when updating as well, unclear what changed.17:53
tpbTitle: Placer fails with final cost check error · Issue #485 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)17:53
litghostkem_: I'm going to bisect to see if I can find when the regression was introduced17:53
kem_litghost: Yeah I've seen that a couple of times as well. It relates to the difference between calculating incremental cost changes vs calculating costs from scratch, which can result in differing floating point round-off17:56
kem_litghost: Bisecting it would be good17:56
kem_litghost: Although it may not be a particular change which is the root cause... it could just be a particular change causes a different optimization path to be followed which results in the round-off differences exceeding the current thershold17:57
litghostkem_: Is https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/483 something VPR could accept?  It's unclear if this is a bug in VPR or a requirement on tiles18:06
tpbTitle: Allow tiles with only sources or sinks. by litghost · Pull Request #483 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)18:06
kem_litghost: We've usually modelled I/Os as being bi-directional (since most FPGA pins can be configured either way).18:10
kem_litghost:  I don't see any problem allowing dedicated inputs/outputs with a single source/sink, so long as any code depending there being both is updated to work.18:11
litghostkem_: I think https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/483 is the only change, as the testarch in https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/485 does route with https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/48318:12
tpbTitle: Allow placement of tiles with only sources or sinks. by litghost · Pull Request #483 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)18:12
litghostkem_: https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/485#issuecomment-47021362018:17
litghostI've tracked down the regression to the "cluster_seed_type".  It does mean I have a workaround, but does that help point you to a fix?18:17
tpbTitle: Placer fails with final cost check error · Issue #485 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)18:17

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