systemc: Check for time overflow in sc_start.

A regression tests checks this situation.

Change-Id: I7716bf7c8cf219c372ab9722fc0ad52e7e674b17
Reviewed-on: https://gem5-review.googlesource.com/12256
Reviewed-by: Gabe Black <gabeblack@google.com>
Maintainer: Gabe Black <gabeblack@google.com>

diff --git a/src/systemc/core/sc_main.cc b/src/systemc/core/sc_main.cc
index 39f6e174b9001572d7d783c3f7d6b3991591bde9..ea243bf61d40b4d1ac5f8b55825fdbd6ea7f8f20 100644 (file)
--- a/src/systemc/core/sc_main.cc
+++ b/src/systemc/core/sc_main.cc
@@ -194,6 +194,10 @@ sc_start(const sc_time &time, sc_starvation_policy p)
         ::sc_gem5::scheduler.oneCycle();
     } else {
         Tick now = ::sc_gem5::scheduler.getCurTick();
+        if (MaxTick - now < time.value()) {
+            SC_REPORT_ERROR("(E544) simulation time value overflow, "
+                    "simulation aborted", "");
+        }
         ::sc_gem5::scheduler.start(now + time.value(), p == SC_RUN_TO_TIME);
     }
 }