Hi all, I just debugged a problem with restoring from checkpoint while specifying maxticks [sic] on the command line. In the process, I noticed that the maxtime parameter is really messed up. Since at least as far back as changeset 8920, the maxtime parameter has been completely masked by the default setting of the maxticks [sic] parameter. Further, when maxtime is specified run() is supposed call m5.ticks.seconds(), a function that isn't even part of the repository anymore, and so even if I tweak the conditionals so that maxtime is checked correctly, I get a Python runtime error when run() calls m5.ticks.seconds(). My feel is that this command line option should be deprecated and it's usage should be removed completely (maybe even remove the option?).
Is anyone using maxtime, and do we care to continue supporting it? Thanks, Joel -- Joel Hestness PhD Student, Computer Architecture Dept. of Computer Science, University of Wisconsin - Madison http://www.cs.utexas.edu/~hestness _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
