summaryrefslogtreecommitdiff
path: root/src/mem/ruby/system/System.cc
diff options
context:
space:
mode:
authorSteve Reinhardt <steve.reinhardt@amd.com>2013-10-15 18:22:49 -0400
committerSteve Reinhardt <steve.reinhardt@amd.com>2013-10-15 18:22:49 -0400
commitb10ff075b102b2a2e4abf5d22735b919a8fda1a9 (patch)
treef4cb14cc72e47b2d681b5f29cc01ae54a00152ae /src/mem/ruby/system/System.cc
parentfe61a074a2563e7e5d7d57f0b0ce2158f651e883 (diff)
downloadgem5-b10ff075b102b2a2e4abf5d22735b919a8fda1a9.tar.xz
ruby: eliminate non-determinism from ruby.stats output
Get rid of non-deterministic "stats" in ruby.stats output such as time & date of run, elapsed & CPU time used, and memory usage. These values cause spurious miscomparisons when looking at output diffs (though they don't affect regressions, since the regressions pass/fail status currently ignores ruby.stats entirely). Most of this information is already captured in other places (time & date in stdout, elapsed time & mem usage in stats.txt), where the regression script is smart enough to filter it out. It seems easier to get rid of the redundant output rather than teaching the regression tester to ignore the same information in two different places.
Diffstat (limited to 'src/mem/ruby/system/System.cc')
-rw-r--r--src/mem/ruby/system/System.cc6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/mem/ruby/system/System.cc b/src/mem/ruby/system/System.cc
index 1f209f785..016169bcc 100644
--- a/src/mem/ruby/system/System.cc
+++ b/src/mem/ruby/system/System.cc
@@ -136,12 +136,6 @@ RubySystem::~RubySystem()
void
RubySystem::printStats(ostream& out)
{
- const time_t T = time(NULL);
- tm *localTime = localtime(&T);
- char buf[100];
- strftime(buf, 100, "%b/%d/%Y %H:%M:%S", localTime);
- out << "Real time: " << buf << endl;
-
m_profiler_ptr->printStats(out);
}