RE: [sv-ec] Update proposal for 1371 $exit

Dave,

 

You proposal again modified the intended semantics of $exit.

 

I think the phrase "disable all initial blocks" is not specific enough.
It seems to imply that *only* the processes that correspond to the
initial blocks are disabled, when the intent is to terminate all
processes spawned by those initial blocks, including all descendant
processes. Also, the term disable might imply that the processes may be
re-enabled when they are in fact terminated.

 

Also, it's not clear what the following sentence means

"Calling $exit from a thread originating from outside an initial block
in a program ..."

I know what you're trying to say, but the use of outside is confusing -
to me that implies some sort of lexical containment. Perhaps,

            Calling $exit from a thread that does not originate in an
initial block in a program ..."

 

Finally, how does this interact with Seven Sharp's proposal to consider
only a thread's existing scheduling region? Your proposal might be to be
at odds with that concept in the sense that the run-time would need to
maintain a thread's origin.

 

            Arturo

 

________________________________

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
Rich, Dave
Sent: Friday, January 26, 2007 7:53 AM
To: sv-ec@eda-stds.org
Subject: [sv-ec] Update proposal for 1371 $exit

 

A new proposal has been uploaded reflecting the comments of the 1/22/07
sv-ec meeting.

 

David Rich
Verification Technologist
Design Verification & Test Division
Mentor Graphics Corporation
dave_rich@mentor.com
Office:   408 487-7206
Cell:     510 589-2625

 


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