As our funcsim will be a part of clock-precise simulator one day, it should be
controllable by external entities. At the moment we start a simulation process
with `void core::run()` method. This should be changed to the following scheme:
* the main execution is run by `int core::run(int requested)' i.e. we specify that a core should execute no more than requested instructions, and it will return the amount of actually performed actions (which might be less). That is a functional core.
* a separate object called scheduler is responsible of calling the core and of interacting with user. That is a scheduler
* Functional core should provide interface that can be later used by clock-precise part.
Thus, we'll be able to build two distinctive simulators on the same functioanl
core - funcsim (core + sceduler) and clock-presise (core + clockl model).
Original issue reported on code.google.com by grigory....@gmail.com on 26 Oct 2010 at 5:02
Original issue reported on code.google.com by
grigory....@gmail.com
on 26 Oct 2010 at 5:02