cpu-o3: Mark getWritableRegOperand() in O3CPU as a regwrite
As discussed here, [1], O3CPU counts getWritableRegOperand() as a reg read, while SimpleCPU variants count getWriableRegOperand() as a reg write. This patch fixes this inconsistency. Here, I assume that if getWritableRegOperand() is used, setReg() will not be used again to write to the destination register. [1] https://github.com/gem5/gem5/pull/341 Change-Id: If00049eb598f6722285e9e09419aef98ceed759f Signed-off-by: Hoa Nguyen <hn@hnpl.org>
This commit is contained in:
@@ -989,10 +989,10 @@ CPU::getWritableReg(PhysRegIdPtr phys_reg, ThreadID tid)
|
|||||||
{
|
{
|
||||||
switch (phys_reg->classValue()) {
|
switch (phys_reg->classValue()) {
|
||||||
case VecRegClass:
|
case VecRegClass:
|
||||||
executeStats[tid]->numVecRegReads++;
|
executeStats[tid]->numVecRegWrites++;
|
||||||
break;
|
break;
|
||||||
case VecPredRegClass:
|
case VecPredRegClass:
|
||||||
executeStats[tid]->numVecPredRegReads++;
|
executeStats[tid]->numVecPredRegWrites++;
|
||||||
break;
|
break;
|
||||||
default:
|
default:
|
||||||
break;
|
break;
|
||||||
|
|||||||
Reference in New Issue
Block a user