[Tool] Comment on the memory efficiency on fabric bitstream address storage
This commit is contained in:
parent
7e940980e1
commit
6b25cf720d
|
@ -207,6 +207,10 @@ class FabricBitstream {
|
|||
* to the configuration protocol directly
|
||||
*
|
||||
* We use a 2-element array, as we may have a BL address and a WL address
|
||||
*
|
||||
* TODO: use nested vector may cause large memory footprint
|
||||
* when bitstream size increases
|
||||
* NEED TO THINK ABOUT A COMPACT MODELING
|
||||
*/
|
||||
vtr::vector<FabricBitId, std::vector<char>> bit_addresses_;
|
||||
vtr::vector<FabricBitId, std::vector<char>> bit_wl_addresses_;
|
||||
|
|
Loading…
Reference in New Issue