cpu-o3: added _amo_op parameter in o3 LSQ
authorJordi Vaquero <jordi.vaquero@metempsy.com>
Fri, 26 Jul 2019 14:31:39 +0000 (16:31 +0200)
committerJordi Vaquero <jordi.vaquero@metempsy.com>
Wed, 7 Aug 2019 17:19:22 +0000 (17:19 +0000)
commit7cb1010bdedb613b06fcf2cb582e14c57d1d794f
tree47cd96527975bca62b3181f97943ce145dc50df3
parent5f0ffd5d49ee5907847f398bbd976f0ebb785e36
cpu-o3: added _amo_op parameter in o3 LSQ

Fix bug with AMO (or RMW) instructions where the amo_op variable
is not being propagated to the LSQ request.

Change-Id: I60c59641d9b497051376f638e27f3c4cc361f615
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/19814
Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>
Maintainer: Anthony Gutierrez <anthony.gutierrez@amd.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com>
Reviewed-by: Anthony Gutierrez <anthony.gutierrez@amd.com>
src/cpu/o3/lsq.hh