f62d1862e0
The parseParam and showParam functions partially worked using template specialization, and partially worked using function overloading. The template specialization could be resolved later once other functions were added, but the regular function overloads could not. That meant that it was practically impossible to add new definitions of those two functions local to the types they worked with. Also, because C++ does not allow partial specialization of template functions, it would not be possible to truly use specialization to wire in BitUnion types. To fix these problems, these functions have been turned into structs which wrap static functions. These can be partially specialized as desired, making them compatible with BitUnions. Also, it's not possible to overload structures like it is with functions, so only specialization is considered, not overloading. While making these changes, these functions (now structs) were also reworked so that they share implementation more, and are generally more streamlined. Given the fact that the previous parseParam and showParam functions could not actually be expanded beyond serialize.hh, and were not actually called directly by any code outside of that file, they should have never been considered part of the API. Now that these structs actually *can* be specialized outside of this file, they should be considered part of the interface. Change-Id: Ic8e677b97fda8378ee1da1f3cf6001e02783fde3 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/36280 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Reviewed-by: Richard Cooper <richard.cooper@arm.com> Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com> Maintainer: Andreas Sandberg <andreas.sandberg@arm.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.