From 6d1e9ee7c573868519f18a6c8427c54cb3bfddb5 Mon Sep 17 00:00:00 2001 From: "Daniel R. Carvalho" Date: Fri, 7 Dec 2018 10:50:31 +0100 Subject: [PATCH] mem-cache: Workaround for setWhenReady assertion Change 174da8e2da6a896d2e97bc264f9c827a0f4c35ac added an assert that is not satisfiable with current implementation, breaking some regression tests. Change-Id: Ibafaf0c51906384364f0b2a4b931f8ec6126d858 Signed-off-by: Daniel R. Carvalho Reviewed-on: https://gem5-review.googlesource.com/c/14955 Reviewed-by: Giacomo Travaglini Reviewed-by: Nikos Nikoleris Maintainer: Nikos Nikoleris --- src/mem/cache/cache_blk.hh | 1 - 1 file changed, 1 deletion(-) diff --git a/src/mem/cache/cache_blk.hh b/src/mem/cache/cache_blk.hh index 9ace496ce..611ce448d 100644 --- a/src/mem/cache/cache_blk.hh +++ b/src/mem/cache/cache_blk.hh @@ -284,7 +284,6 @@ class CacheBlk : public ReplaceableEntry */ void setWhenReady(const Tick tick) { - assert((whenReady == MaxTick) || (tick >= whenReady)); assert(tick >= tickInserted); whenReady = tick; } -- 2.30.2