mem-cache: Remove extra block init in BaseSetAssoc

Removed extra initialization of cache block just after they have been
created and organized the comments.

Change-Id: I75c1beaf0489e3e530fd8cbff2739dc7593e3e6f
Reviewed-on: https://gem5-review.googlesource.com/8661
Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
Reviewed-by: Nikos Nikoleris <nikos.nikoleris@arm.com>
Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com>
This commit is contained in:
Daniel R. Carvalho
2018-02-27 14:31:59 +01:00
committed by Daniel Carvalho
parent 3c076e4d69
commit 2a71435550

View File

@@ -85,24 +85,25 @@ BaseSetAssoc::BaseSetAssoc(const Params *p)
// link in the data blocks
for (unsigned j = 0; j < assoc; ++j) {
// locate next cache block
BlkType *blk = &blks[blkIndex];
// Select block within the set to be linked
BlkType*& blk = sets[i].blks[j];
// Locate next cache block
blk = &blks[blkIndex];
// Associate a data chunk to the block
blk->data = &dataBlks[blkSize*blkIndex];
++blkIndex;
// invalidate new cache block
blk->invalidate();
//EGH Fix Me : do we need to initialize blk?
// Setting the tag to j is just to prevent long chains in the hash
// table; won't matter because the block is invalid
// Setting the tag to j is just to prevent long chains in the
// hash table; won't matter because the block is invalid
blk->tag = j;
blk->whenReady = 0;
blk->isTouched = false;
sets[i].blks[j]=blk;
// Set its set and way
blk->set = i;
blk->way = j;
// Update block index
++blkIndex;
}
}
}