You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/src/vpr/command_line_usage.rst
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1120,6 +1120,14 @@ VPR uses a negotiated congestion algorithm (based on Pathfinder) to perform rout
1120
1120
1121
1121
.. seealso:: :ref:`timing_driven_router_options`
1122
1122
1123
+
.. option:: --flat_routing{on|off}
1124
+
1125
+
If this option is enabled, the *run-flat* router is used instead of the *two-stage* router.
1126
+
This means that during the routing stage, all nets, both intra- and inter-cluster, are routed directly from one primitive pin to another primitive pin.
1127
+
This increases routing time but can improve routing quality by re-arranging LUT inputs and exposing additional optimization opportunities in architectures with local intra-cluster routing that is not a full crossbar.
1128
+
1129
+
**Default:** ``OFF`
1130
+
1123
1131
.. option:: --max_router_iterations <int>
1124
1132
1125
1133
The number of iterations of a Pathfinder-based router that will be executed before a circuit is declared unrouteable (if it hasn’t routed successfully yet) at a given channel width.
// If the SPEC_CPU flag is set, we need to make sure that all floating point numbers are perfectly representable in
355
+
// binary format. Thus, we changed the IPIN_COST_INDEX base cost from 0.95 to 0.875.
356
+
// This number is perfectly representable in a binary mantissa (without round-off) so we can get the same routing result on different platforms.
357
+
// Since the router cost calculations and heap use floating point numbers, normally we get slightly different round off with different compiler settings,
358
+
// leading to different heap sorts and hence different routings.
359
+
// To make result validation for SPEC easier, we choose all router parameters to result in calculations that fit perfectly in a 24-bit binary mantissa.
360
+
// .875 = 1/2 + 1/4 + 1/8 can be perfectly represented in a binary mantissa with only the first 3 bits set.
0 commit comments