Daniel R. Carvalho 75035f5674 mem-ruby: Use Packet writing functions instead of memcpy ...

Classes were using memcpy instead of the Packet functions
created for writing to/from the packet. This allows these
writes to be better checked and tracked.

Change-Id: Iae3fba1351330916ee1d4103809c71e151b1639e
Signed-off-by: Daniel R. Carvalho <odanrc@yahoo.com.br>
Reviewed-on: https://gem5-review.googlesource.com/c/13915
Reviewed-by: Nikos Nikoleris <nikos.nikoleris@arm.com>
Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com>

2018-11-07 19:34:55 +00:00

..

common

style: fix amd license and style issues

2018-05-16 15:32:01 +00:00

filters

mem: Standardize mem folder header guards

2018-02-06 10:26:27 +00:00

network

mem-ruby: Fix a bug in MessageBuffer randomization

2018-09-24 21:06:38 +00:00

profiler

ruby: guard usage of GPUCoalescer code in Profiler

2017-01-19 11:59:34 -05:00

slicc_interface

mem-ruby: Use Packet writing functions instead of memcpy

2018-11-07 19:34:55 +00:00

structures

ruby: remove unused code inside '#if 0 ... #endif'

2018-08-17 17:19:12 +00:00

system

mem-ruby: Use Packet writing functions instead of memcpy

2018-11-07 19:34:55 +00:00

SConscript

scons,ruby: do not generate unnecessary files

2018-08-17 17:21:02 +00:00