derek/gem5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix a memory leak in the memtester

Browse Source 
--HG--
extra : convert_revision : 93062b0f1a3ba7a5210e2f27099f20ae8f66522b
This commit is contained in:
Ron Dreslinski
2006-10-12 13:43:12 -04:00
parent ba4c224c39
commit dd18ffe51d
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
src/cpu/memtest/memtest.cc
View File

@@ -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);
/*