8b3565d50790db9683fb85ba00d51a5e1e1c58a2
Don't cache the first version requested of object files to use for subsequent requests. This was originally put in place to avoid an error when object files could be built with trivially different command lines, ie command lines which are technically different but not in a necessarily meaningful way, or less seriously a warning when the command lines were the same. The warning was disabled in an earlier change, and the error was avoided by using a different object file suffix when building unit tests. This helps avoid bugs if the object files actually *would* turn out to be different in a meaningful way based on the flags used, and simplifies the build. Change-Id: I6b90e6e36b13adb73e587bb8fc533984f764d95a Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/48138 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Maintainer: Gabe Black <gabe.black@gmail.com> Tested-by: kokoro <noreply+kokoro@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.
Description