config: Initialize and check cpt_starttick
authorJoel Hestness <jthestness@gmail.com>
Wed, 11 Sep 2013 20:34:21 +0000 (15:34 -0500)
committerJoel Hestness <jthestness@gmail.com>
Wed, 11 Sep 2013 20:34:21 +0000 (15:34 -0500)
commit073b27c257da7118e3b17a0dc77d9da1ac863621
tree2a4f0ca1edd443db0660dcdf6995959112b4288a
parentc1cf55c7388d01222825911fabca617177966ce9
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.
configs/common/Simulation.py