RE: [sv-bc] function task calling

I think the main "task-like" item of concern here is the

ability to block process execution with a time controlling

statement.

 

It simply doesn't make sense for a function call in the

middle of an expression to suspend the calling process,

and then resume it at some future time unit (or even

the same time unit, if a #0 was encountered).

 

Other constructs that used to be illegal in functions have

been removed from the "restricted list".  (e.g. nonblocking

assigns, fork-join_none, etc.)

 

I think that Section 13.2 in P1800-2008_D3 should probably

be modified a little bit to distinguish native SV tasks from

system tasks in the second bullet item in the bullet list.

It should be fine to call any system task or function from

within a native SV function.

 

I can't think of any system task that can behave the same

as a time-controlling statement, effectively blocking the

simulation kernel and enabling a different process to run.

 

BTW, time-controlling statements are #, @, and wait,

as far as I recall.

 

Thanks,

Doug

 

 

 

From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On
Behalf Of Brad Pierce
Sent: Monday, September 03, 2007 9:07 PM
To: sv-bc
Subject: Re: [sv-bc] function task calling

 

Is there anything task-like about $display, or should it really be a
void system function?

 

-- Brad

 

________________________________

From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
Bresticker, Shalom
Sent: Monday, September 03, 2007 5:30 AM
To: sv-bc
Subject: [sv-bc] function task calling

Since functions are not allowed to call tasks, how can a function
contain a call to $display? 

What types of built-in system tasks are functions allowed to call? 

Shalom 

Shalom Bresticker 
Intel Jerusalem LAD DA 
+972 2 589-6852 
+972 54 721-1033 


-- 
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 <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.