From f6742ea26e1a1cac21b486c7c5adad6fb6304e92 Mon Sep 17 00:00:00 2001 From: Ali Saidi Date: Sun, 25 Jan 2015 07:22:26 -0500 Subject: cpu: Remove all notion that we know when the cpu is misspeculating. We have no way of knowing if a CPU model is on the wrong path with our execute-in-execute CPU models. Don't pretend that we do. --- src/cpu/thread_context.hh | 6 ------ 1 file changed, 6 deletions(-) (limited to 'src/cpu/thread_context.hh') diff --git a/src/cpu/thread_context.hh b/src/cpu/thread_context.hh index 95d89dcc5..850ff9468 100644 --- a/src/cpu/thread_context.hh +++ b/src/cpu/thread_context.hh @@ -255,9 +255,6 @@ class ThreadContext virtual void setStCondFailures(unsigned sc_failures) = 0; - // Only really makes sense for old CPU model. Still could be useful though. - virtual bool misspeculating() = 0; - // Same with st cond failures. virtual Counter readFuncExeInst() = 0; @@ -462,9 +459,6 @@ class ProxyThreadContext : public ThreadContext void setStCondFailures(unsigned sc_failures) { actualTC->setStCondFailures(sc_failures); } - // @todo: Fix this! - bool misspeculating() { return actualTC->misspeculating(); } - void syscall(int64_t callnum) { actualTC->syscall(callnum); } -- cgit v1.2.3