changeset 569e1f1d762d in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=569e1f1d762d
description:
        cache: remove drainManager because it's not used

        the cache drainManager is set but never cleared, this is because
        the cache itself does not need to be drained and thus never
        triggers a signalDrainDone(). because the drainManager variable
        is not used properly and does not appear to be necessary it has
        been removed with this patch.

diffstat:

 src/mem/cache/base.cc |  3 ---
 src/mem/cache/base.hh |  3 ---
 2 files changed, 0 insertions(+), 6 deletions(-)

diffs (33 lines):

diff -r 5dca39cc7641 -r 569e1f1d762d src/mem/cache/base.cc
--- a/src/mem/cache/base.cc     Mon Jan 28 08:24:40 2013 -0600
+++ b/src/mem/cache/base.cc     Mon Jan 28 20:19:42 2013 -0500
@@ -77,7 +77,6 @@
       blocked(0),
       noTargetMSHR(NULL),
       missCount(p->max_miss_count),
-      drainManager(NULL),
       addrRanges(p->addr_ranges.begin(), p->addr_ranges.end()),
       system(p->system)
 {
@@ -752,8 +751,6 @@
 
     // Set status
     if (count != 0) {
-        drainManager = dm;
-
         setDrainState(Drainable::Draining);
         DPRINTF(Drain, "Cache not drained\n");
         return count;
diff -r 5dca39cc7641 -r 569e1f1d762d src/mem/cache/base.hh
--- a/src/mem/cache/base.hh     Mon Jan 28 08:24:40 2013 -0600
+++ b/src/mem/cache/base.hh     Mon Jan 28 20:19:42 2013 -0500
@@ -287,9 +287,6 @@
     /** The number of misses to trigger an exit event. */
     Counter missCount;
 
-    /** The drain event. */
-    DrainManager *drainManager;
-
     /**
      * The address range to which the cache responds on the CPU side.
      * Normally this is all possible memory addresses. */
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to