d64173549b
All other considerations aside, DTRACE probably fits best in trace.hh where it is now, but unfortunately that creates an awkward dependence between that file and eventq.hh and eventq_impl.hh. DTRACE only depends on flags in the Debug namespace and a universal macro TRACING_ON, so even though it won't be alongside the things it's most logically associated with, it will be alongside all of its dependencies. An alternative would be to re-implement DTRACE in eventq_impl.hh which wouldn't be too big of a problem because it's so simple, but it's cleaner and less error prone to still keep a single definition. Because base/trace.hh includes base/debug.hh, any consumers expecting to find DTRACE in base/trace.hh will still get that definition, even though it's no longer direct. Change-Id: I0dac83295891630686c3a8038eb54138cf40ab44 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/29411 Maintainer: Gabe Black <gabeblack@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Jason Lowe-Power <power.jg@gmail.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.