Subject: [sv-ec] Non-blocking Event Trigger
From: Jay Lawrence (lawrence@cadence.com)
Date: Fri Mar 14 2003 - 04:42:16 PST
While we are making progress on the persistent event proposal, we never
did vote on my non-blocking event trigger proposal. The following is a
restatement of the proposal originally mailed out for consideration on
January 6, 2003 for a non-blocking event trigger operator. The intent
of this proposal is to allow a simple way to the event trigger until
NBA-time to partially disambiguate the triggering of events in exactly
the same way that non-blocking assignments disambiguated assignment many
years ago.
---------
Proposal:
---------
The extensions to 1364 syntax would be:
Add to the 'statement' production in A.6.4:
statement ::=
...
{ attribute_instance } nonblocking_event_trigger
Add in section A.6.5:
nonblocking_event_trigger ::=
->> [delay_or_event_control]
hierarchical_event_identifier ;
The effect of this operator is that the statement executes without
blocking and it creates a non-blocking assign update event in the time
when the delay control expires, or the event-control occurs. The effect
of this update event would be to trigger the referenced event in the
nonblocking assignment region of the simulation cycle.
Jay
===================================
Jay Lawrence
Architect - Functional Verification
Cadence Design Systems, Inc.
(978) 262-6294
lawrence@cadence.com
===================================
This archive was generated by hypermail 2b28 : Fri Mar 14 2003 - 04:43:22 PST