0eab4bf2af
With some exceptions (in arm/x86) the standard memory read/write interface for instructions relies upon the helper functions in src/arch/generic/memhelpers.hh which wrap the ExecContext interface. (readMem, writeMem...) Those helpers rely on the source/destination data to be provided (as expected) but not on the size of the transaction. The latter gets evaluated via the host size of the source/destination data (sizeof(MemT)). For this reason some instructions, which are instead using an incompatible MemT data (as an example, a SIMD operation loading data in an array of integers), make direct use of the ExecContext interface, which is simply requesting for a pointer and a number of bytes. Some other instructions are using the ExecContext interface since the helpers do not accept a byteEnable argument. This patch is adding some helpers to address these issues. The idea is to deprecate direct usage of the ExecContext APIs. These new wrappers do not work with the type detection mechanism to evaluate the number of bytes we are accessing. JIRA: https://gem5.atlassian.net/browse/GEM5-196 Change-Id: I5b822d278bdf325a68a01aa1861b6487c6628245 Signed-off-by: Giacomo Travaglini <giacomo.travaglini@arm.com> Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/23527 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Gabe Black <gabeblack@google.com> Reviewed-by: Daniel Carvalho <odanrc@yahoo.com.br> Maintainer: Gabe Black <gabeblack@google.com>
This is the gem5 simulator. The main website can be found at http://www.gem5.org A good starting point is http://www.gem5.org/about, and for more information about building the simulator and getting started please see http://www.gem5.org/documentation and http://www.gem5.org/documentation/learning_gem5/introduction. To build gem5, you will need the following software: g++ or clang, Python (gem5 links in the Python interpreter), SCons, SWIG, zlib, m4, and lastly protobuf if you want trace capture and playback support. Please see http://www.gem5.org/documentation/general_docs/building for more details concerning the minimum versions of the aforementioned tools. Once you have all dependencies resolved, type 'scons build/<ARCH>/gem5.opt' where ARCH is one of ARM, NULL, MIPS, POWER, SPARC, or X86. This will build an optimized version of the gem5 binary (gem5.opt) for the the specified architecture. See http://www.gem5.org/documentation/general_docs/building for more details and options. The basic source release includes these subdirectories: - configs: example simulation configuration scripts - ext: less-common external packages needed to build gem5 - src: source code of the gem5 simulator - system: source for some optional system software for simulated systems - tests: regression tests - util: useful utility programs and files To run full-system simulations, you will need compiled system firmware (console and PALcode for Alpha), kernel binaries and one or more disk images. If you have questions, please send mail to gem5-users@gem5.org Enjoy using gem5 and please share your modifications and extensions.