Just for clarification...
I assume the concept of "no activity" includes "no opportunity to move time forward". In other words, if there are no pending processes, but a timed notification or wait, then the simulator should move the clock forward. Should this cause a warning or not. I would argue no. All timed events will result in some activity or eventual starvation (since something has to put the events in the queue in the first place, and conceptually with the intent some process will act on the events):
wait(10,SC_NS);
sc_event my_event;
my_event.notify(10,SC_NS);
Even if no process were waiting for my_event, the act of notification is itself an activity. Hence no warning.
With the above assumptions, I agree with Philipp's proposal.
On Jan 11, 2011, at 7:26 AM, john.aynsley@doulos.com wrote:
> All,
>
> Philipp writes:
>
> 5.3.4.2 Function sc_start
>
> "When function sc_start is called with a zero-valued time argument, the scheduler shall run for one delta cycle,…"
>
> Should there be a warning, if no activity is due in that delta cycle (sc_pending_activity_at_current_time() == false)? Otherwise, one can easily run into an endless loop…
>
>
> Opinions?
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
------------------------------------------------------
David C Black, System-Level Specialist
XtremeEDA USA Corporation http://www.Xtreme-EDA.com
(Consulting, Services & Training for all your ESL design assurance needs)
Voice: 512.850.4322 Skype: dcblack FAX: 888.467.4609
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Jan 11 08:41:23 2011
This archive was generated by hypermail 2.1.8 : Tue Jan 11 2011 - 08:41:26 PST