cpu: Fix a = that was supposed to be a == in an assert.
authorGabe Black <gabeblack@google.com>
Mon, 25 May 2020 11:25:49 +0000 (04:25 -0700)
committerGabe Black <gabeblack@google.com>
Mon, 25 May 2020 21:05:41 +0000 (21:05 +0000)
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>
src/cpu/kvm/base.cc

index 38fea199705f1ded97354cc59a2ffa75cc20d372..d44bb3d23252d8c91eef19358c3ba64b31fdf79e 100644 (file)
@@ -223,7 +223,7 @@ BaseKvmCPU::KVMCpuPort::recvReqRetry()
 void
 BaseKvmCPU::finishMMIOPending()
 {
-    assert(_status = RunningMMIOPending);
+    assert(_status == RunningMMIOPending);
     assert(!tickEvent.scheduled());
 
     _status = RunningServiceCompletion;