RE: Process control extensions and clocked threads

John,

Good question about clocked threads. The intent is certainly not to allow clocked threads to have regular static sensitivity in addition to a single clock. Is that being implied by allowing a process control construct on clocked threads?

Here are my thoughts about the various process control constructs applying to clocked threads. Need inputs on this.

 *
suspend-resume can techncially apply, but the recommendation would be to use disable/enable, as it is intended clocked threads only run on a clock edge; is it better to make suspend-resume an error? Are there any use cases where one might want to suspend/resume a clocked thread? I'm inlcined to make it be an error
 *
disable-enable certainly appleis, as these constructs were invented for clocked threads only
 *
kill applies
 *
reset is questionable - can make the thread run in between clock edges, which is not intended; should be error?
 *
sync_reset_on() and sync_reset_off() applies
 *
reset_signal_is() applies; async_reset_signal_is() is not intended for the same reason as reset(); error?

Thanks,
-Bishnupriya
________________________________
From: john.aynsley@doulos.com [mailto:john.aynsley@doulos.com]
Sent: Friday, July 23, 2010 8:00 PM
To: Bishnupriya Bhattacharya; systemc-p1666-technical@eda.org
Subject: Process control extensions and clocked threads

Bishnupriya, All,

Which of the process control extensions for thread and method processes apply to clocked threads? All of them? If not, which?

In particular, are we going to allow clocked threads to have regular static sensitivity in addition to having a single clock?

Thanks,

John A

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.