Skip to content

Commit 6c522f7

Browse files
author
MohamedElgammal
committed
remove unused data structure
1 parent 1e357a0 commit 6c522f7

File tree

2 files changed

+0
-9
lines changed

2 files changed

+0
-9
lines changed

vpr/src/place/placer_context.h

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -107,9 +107,6 @@ struct PlacerMoveContext : public Context {
107107

108108
// Container to save the highly critical pins (higher than a timing criticality limit setted by commandline option)
109109
std::vector<std::pair<ClusterNetId, int>> highly_crit_pins;
110-
111-
// Container to save the highly critical blocks (blocks with one or more highly critical pins)
112-
std::unordered_set<ClusterBlockId> highly_crit_blocks;
113110
};
114111

115112
/**

vpr/src/place/timing_place.cpp

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,7 @@ void PlacerCriticalities::update_criticalities(const SetupTimingInfo* timing_inf
5656
}
5757

5858
ClusterBlockId crit_block;
59-
auto& cluster_ctx = g_vpr_ctx.clustering();
6059
auto& place_move_ctx = g_placer_ctx.mutable_move();
61-
place_move_ctx.highly_crit_blocks.clear();
6260

6361
/* Performs a 1-to-1 mapping from criticality to timing_place_crit_.
6462
* For every pin on every net (or, equivalently, for every tedge ending
@@ -93,10 +91,6 @@ void PlacerCriticalities::update_criticalities(const SetupTimingInfo* timing_inf
9391
* Since path criticality varies much more than timing, we "sharpen" timing
9492
* criticality by taking it to some power, crit_exponent (between 1 and 8 by default). */
9593
timing_place_crit_[clb_net][pin_index_in_net] = new_crit;
96-
//timing_place_normalized_crit_[clb_net][pin_index_in_net] = clb_pin_crit;
97-
98-
if (new_crit > crit_params.crit_limit)
99-
place_move_ctx.highly_crit_blocks.insert(cluster_ctx.clb_nlist.net_driver_block(clb_net));
10094
}
10195

10296
/* Criticalities updated. In sync with timing info. */

0 commit comments

Comments
 (0)