summaryrefslogtreecommitdiff
path: root/src/mem/ruby/network/Topology.cc
diff options
context:
space:
mode:
authorJoel Hestness <jthestness@gmail.com>2013-09-11 15:34:21 -0500
committerJoel Hestness <jthestness@gmail.com>2013-09-11 15:34:21 -0500
commit073b27c257da7118e3b17a0dc77d9da1ac863621 (patch)
tree2a4f0ca1edd443db0660dcdf6995959112b4288a /src/mem/ruby/network/Topology.cc
parentc1cf55c7388d01222825911fabca617177966ce9 (diff)
downloadgem5-073b27c257da7118e3b17a0dc77d9da1ac863621.tar.xz
config: Initialize and check cpt_starttick
The previous changeset (9816) that fixes the use of max ticks introduced the variable cpt_starttick, which is used for setting the relative max tick. Unfortunately, with checkpointing at an instruction count or with simpoints, the checkpoint tick is not stored conveniently, so to ensure that cpt_starttick is initialized, set it to 0. Also, if using --rel-max-tick, check the use of instruction counts or simpoints to warn the user that the max tick setting does not include the checkpoint ticks.
Diffstat (limited to 'src/mem/ruby/network/Topology.cc')
0 files changed, 0 insertions, 0 deletions