From: Gabe Black <gabeblack@google.com>
Date: Mon, 25 May 2020 11:25:49 +0000 (-0700)
Subject: cpu: Fix a = that was supposed to be a == in an assert.
X-Git-Tag: v20.1.0.0~628
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=997b74166baf1ac7a43b758f81b4d5e442a04428;p=gem5.git

cpu: Fix a = that was supposed to be a == in an assert.

The KVM CPU has a _status field which is checked by an assert, but
rather than checking it with an ==, it accidentally used a =.

Change-Id: Ic1970d232786af6666c4ec2719c70f3f1509277c
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/29405
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
---

diff --git a/src/cpu/kvm/base.cc b/src/cpu/kvm/base.cc
index 38fea1997..d44bb3d23 100644
--- a/src/cpu/kvm/base.cc
+++ b/src/cpu/kvm/base.cc
@@ -223,7 +223,7 @@ BaseKvmCPU::KVMCpuPort::recvReqRetry()
 void
 BaseKvmCPU::finishMMIOPending()
 {
-    assert(_status = RunningMMIOPending);
+    assert(_status == RunningMMIOPending);
     assert(!tickEvent.scheduled());
 
     _status = RunningServiceCompletion;