RE: [sv-ec] blocking statement

From: Rich, Dave <Dave_Rich@mentor.com>
Date: Tue Jan 26 2010 - 07:36:57 PST

The definition of a blocking statement comes from the definition of a
blocking assignment in 4.9.3

"causes the executing process to be suspended and scheduled as a future
event."

 

The LRM also refers to timing or event controls as blocking, as well as
wait(). A task call is a potentially blocking statement only in the
context of a function call. Verilog was more consistent in its
definition of blocking. However, SV was less consistent in new features.
For example in mailboxes, try_put() is defined as non-blocking, by there
is no mention of blocking for put().

 

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
Lavva, Irina
Sent: Tuesday, January 26, 2010 12:53 AM
To: Daniel Mlynek; sv-ec@eda.org
Subject: RE: [sv-ec] blocking statement

 

Indeed I did not find a definition of "blocking statement" too, the
only definition that I found this:

"The expect statement is a procedural blocking statement that allows
waiting on a property evaluation"

 

      Irina

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
Daniel Mlynek
Sent: Tuesday, January 26, 2010 10:42 AM
To: sv-ec@eda.org
Subject: [sv-ec] blocking statement

 

What is the blocking statement? ie used in below definition. There is no
definition of blocking statement in LRM.

 

"The parent process continues to execute concurrently with all the
processes spawned by the fork. The spawned processes do not start
executing until the parent thread executes a blocking statement."

 

DANiel

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner <http://www.mailscanner.info/> , and is
believed to be clean. 
---------------------------------------------------------------------
Intel Israel (74) Limited
 
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner <http://www.mailscanner.info/> , and is
believed to be clean. 
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Jan 26 07:38:17 2010

This archive was generated by hypermail 2.1.8 : Tue Jan 26 2010 - 07:38:45 PST