summaryrefslogtreecommitdiff
path: root/src/sim/simulate.cc
diff options
context:
space:
mode:
authorNathan Binkert <nate@binkert.org>2008-10-10 10:18:28 -0700
committerNathan Binkert <nate@binkert.org>2008-10-10 10:18:28 -0700
commitafb279b1bb8f7c01a74c4fe783ce14365916e920 (patch)
treebac1446af4bc5241c2d94e98e86346dff505b43b /src/sim/simulate.cc
parentb25e56b32a3af5d11680b465f6443c73156ddf86 (diff)
downloadgem5-afb279b1bb8f7c01a74c4fe783ce14365916e920.tar.xz
output: Make panic/fatal/warn more flexible so we can add some new ones.
The major thrust of this change is to limit the amount of code duplication surrounding the code for these functions. This code also adds two new message types called info and hack. Info is meant to be less harsh than warn so people don't get confused and start thinking that the simulator is broken. Hack is a way for people to add runtime messages indicating that the simulator just executed a code "hack" that should probably be fixed. The benefit of knowing about these code hacks is that it will let people know what sorts of inaccuracies or potential bugs might be entering their experiments. Finally, I've added some flags to turn on and off these message types so command line options can change them.
Diffstat (limited to 'src/sim/simulate.cc')
-rw-r--r--src/sim/simulate.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/sim/simulate.cc b/src/sim/simulate.cc
index 59d79b7c6..7f40805e6 100644
--- a/src/sim/simulate.cc
+++ b/src/sim/simulate.cc
@@ -47,7 +47,7 @@
SimLoopExitEvent *
simulate(Tick num_cycles)
{
- warn("Entering event queue @ %d. Starting simulation...\n", curTick);
+ info("Entering event queue @ %d. Starting simulation...\n", curTick);
if (num_cycles < 0)
fatal("simulate: num_cycles must be >= 0 (was %d)\n", num_cycles);