Searched hist:11070 (Results 1 - 2 of 2) sorted by relevance
/gem5/src/sim/ | ||
H A D | sim_events.cc | 11070:d9560edaf0a9 Tue Sep 01 08:41:00 EDT 2015 Andreas Sandberg <andreas.sandberg@arm.com> sim: Remove autoserialize support for exit events This changeset removes the support for the autoserialize parameter in GlobalSimLoopExitEvent (including exitSimLoop()) and LocalSimLoopExitEvent. Auto-serialization of the LocalSimLoopExitEvent was never used, so this is not expected to affect anything. However, it was sometimes used for GlobalSimLoopExitEvent. Unfortunately, serialization of global events has never been supported, so checkpoints with such events will currently cause simulation panics. The serialize parameter to exitSimLoop() has been left in-place to maintain API compatibility (removing it would affect m5ops). Instead of just dropping it, we now print a warning if the parameter is set and the exit event is scheduled in the future (i.e., not at the current tick). |
H A D | sim_events.hh | 11070:d9560edaf0a9 Tue Sep 01 08:41:00 EDT 2015 Andreas Sandberg <andreas.sandberg@arm.com> sim: Remove autoserialize support for exit events This changeset removes the support for the autoserialize parameter in GlobalSimLoopExitEvent (including exitSimLoop()) and LocalSimLoopExitEvent. Auto-serialization of the LocalSimLoopExitEvent was never used, so this is not expected to affect anything. However, it was sometimes used for GlobalSimLoopExitEvent. Unfortunately, serialization of global events has never been supported, so checkpoints with such events will currently cause simulation panics. The serialize parameter to exitSimLoop() has been left in-place to maintain API compatibility (removing it would affect m5ops). Instead of just dropping it, we now print a warning if the parameter is set and the exit event is scheduled in the future (i.e., not at the current tick). |
Completed in 18 milliseconds