77869b05b8c03a05b4bc3539daaa32d754ffa8a3
This may be directly in the case of native tests, or through a user level QEMU binary for non-native tests. scons is smart enough to expect to be able to run native tests always, and non-native tests only if a qemu binary has been found. To tell scons to run tests in a particular category, you can use a command of this form: scons build/[category]/test/ where category is either an "abi" like sparc or x86, or "native" for tests which don't do anything target specific and so can be run on the host. There will be two directories under .../tests, "bin" and "result". "bin" is where the test binaries themselves will be built, and "result" is for the results of running those binaries. Change-Id: I6450ab4a97169f8a01292d946bfac18008b0430c Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/27752 Maintainer: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Bobby R. Bruce <bbruce@ucdavis.edu>
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.
Description