ruby: Fix CacheMemory allocate leak
Review Request #3087 - Created Sept. 2, 2015 and submitted - Latest diff uploaded
| Information | |
|---|---|
| Joel Hestness | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 11078:30183e60a824 --------------------------- ruby: Fix CacheMemory allocate leak If a cache entry permission was previously set to NotPresent, but the entry was not deleted, a following cache allocation can cause the entry to be leaked by setting the entry pointer to a newly allocated entry. To eliminate this possibility, check if the new entry is different from the old one, and if so, delete the old one.
