f784097f7a
Most of the time, the type pointed to by a PCState pointer or reference will be the same as all the others, if not nullptr. This change adds a set of "set" functions which assume that the underlying type of each pointer or reference are the same, and handles casting, copying things over, creating a new copy, etc, for you. It uses a new "update" virtual method on PCState subclasses which casts the source to the same type as the destination and copies values over. Note that the "set" function doesn't actually verify that the two types are the same, just like the overloaded ==, != and << operators. In the future, those checks can be added for debugging purposes, probably guarded by a configuration variable which can be toggled on or off to get better performance or more thorough error checking. The main advantage of these wrappers are that they allows consistent semantics whether your moving a value from a pointer, or from a yet unconverted PCState subclass, or vice versa, which will be particularly helpful while transitioning between using raw PCState instances and using primarily pointers and references. This change also adds wrappers which handle std::unique_ptr, which makes it easier to use them as arguments to these functions. Otherwise, if the std::unique_ptr is a temporary value, using the return value of .get() will let the std::unique_ptr go out of scope, making it delete the data pointed to by the returned pointed. By keeping the std::unique_ptr around on the stack, that prevents it from going out of scope. Change-Id: I2c737b08e0590a2c46e212a7b9efa543bdb81ad3 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/52041 Tested-by: kokoro <noreply+kokoro@google.com> Maintainer: Gabe Black <gabe.black@gmail.com> Reviewed-by: Daniel Carvalho <odanrc@yahoo.com.br>
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, 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 these tools. Once you have all dependencies resolved, type 'scons build/<CONFIG>/gem5.opt' where CONFIG is one of the options in build_opts like ARM, NULL, MIPS, POWER, SPARC, X86, Garnet_standalone, etc. This will build an optimized version of the gem5 binary (gem5.opt) with the the specified configuration. See http://www.gem5.org/documentation/general_docs/building for more details and options. The main source tree includes these subdirectories: - build_opts: pre-made default configurations for gem5 - build_tools: tools used internally by gem5's build process. - configs: example simulation configuration scripts - ext: less-common external packages needed to build gem5 - include: include files for use in other programs - site_scons: modular components of the build system - 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 may need compiled system firmware, kernel binaries and one or more disk images, depending on gem5's configuration and what type of workload you're trying to run. Many of those resources can be downloaded from http://resources.gem5.org, and/or from the git repository here: https://gem5.googlesource.com/public/gem5-resources/ If you have questions, please send mail to gem5-users@gem5.org Enjoy using gem5 and please share your modifications and extensions.