Fix a memory leak in the memtester
--HG-- extra : convert_revision : 93062b0f1a3ba7a5210e2f27099f20ae8f66522b
This commit is contained in:
parent
ba4c224c39
commit
dd18ffe51d
|
@ -360,7 +360,11 @@ MemTest::tick()
|
|||
//For now we only allow one outstanding request per addreess per tester
|
||||
//This means we assume CPU does write forwarding to reads that alias something
|
||||
//in the cpu store buffer.
|
||||
if (outstandingAddrs.find(paddr) != outstandingAddrs.end()) return;
|
||||
if (outstandingAddrs.find(paddr) != outstandingAddrs.end()) {
|
||||
delete result;
|
||||
delete req;
|
||||
return;
|
||||
}
|
||||
else outstandingAddrs.insert(paddr);
|
||||
|
||||
// ***** NOTE FOR RON: I'm not sure how to access checkMem. - Kevin
|
||||
|
@ -395,7 +399,12 @@ MemTest::tick()
|
|||
//For now we only allow one outstanding request per addreess per tester
|
||||
//This means we assume CPU does write forwarding to reads that alias something
|
||||
//in the cpu store buffer.
|
||||
if (outstandingAddrs.find(paddr) != outstandingAddrs.end()) return;
|
||||
if (outstandingAddrs.find(paddr) != outstandingAddrs.end()) {
|
||||
delete result;
|
||||
delete req;
|
||||
return;
|
||||
}
|
||||
|
||||
else outstandingAddrs.insert(paddr);
|
||||
|
||||
/*
|
||||
|
|
Loading…
Reference in a new issue