RE: Questions re sync_reset_on/off

I would vote for always allowing sync_reset_on and sync_reset_off for both
thread processes and method processes (regardless of the
include_descendants flag, for simplicity), but suggesting in the LRM that
an implementation may give a warning when the target process instance is a
method process.

John A

From:
Bishnupriya Bhattacharya <bpriya@cadence.com>
To:
"john.aynsley@doulos.com" <john.aynsley@doulos.com>
Cc:
"systemc-p1666-technical@eda.org" <systemc-p1666-technical@eda.org>
Date:
26/07/2010 07:46
Subject:
RE: Questions re sync_reset_on/off

That's an excellent catch John. It would make sense to allow sync_reset_on
and sync_reset_off calls on a method process when include_descendants flag
is set, and issue a warning when the flag is not set. Would that be
consistent?
 
Thanks,
-Bishnupriya

From: john.aynsley@doulos.com [mailto:john.aynsley@doulos.com]
Sent: Friday, July 23, 2010 8:55 PM
To: Bishnupriya Bhattacharya
Cc: systemc-p1666-technical@eda.org
Subject: RE: Questions re sync_reset_on/off

Bishnupriya,

<snip>
* You say it is an error to call sync_reset_on for a method process. What
about sync_reset_off? Is that an error too, or is the implementation
allowed to just ignore it?
[bpriya: good question. I don't feel strongly, but would vote for
sync_reset_off() on a method process is not an error.]
<snip>

Hmmm. What about include_descendants? If sync_reset_on and/or
sync_reset_off were an error for method processes and you had children of
mixed gender, you would get an error trying to modify their sync state
using include_descendants. On the other hand, if both sync_reset_on and
sync_reset_off were ignored for method processes, handling mixed gender
children would be fine - the call would simply pick out the thread
processes.

WHYT?

John A

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