e883a6c970
When defining a static constexpr variable in C++11, it is still required to have a separate definition someplace, something that can be particularly problematic in template classes. C++17 fixes this problem by adding inline variables which don't, but in the mean time having a static constexpr value with no backing store will, if the compiler decides to not fold away the storage location, cause linking errors. This happened to me when trying to build the debug build of ARM just now. By turning these expressions into static inline functions, then they no longer need definitions elsewhere, still fold away to nothing, and are compliant with C++11 which is currently the standard gem5 expects to be using. Change-Id: I647d7cf4a1e8de98251ee9ef116f007e08eac1f3 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/24964 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Chun-Chen TK Hsu <chunchenhsu@google.com> Maintainer: Giacomo Travaglini <giacomo.travaglini@arm.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.