RE: Draft P1666 LRM for review - updated

In 6.2.12 and 6.6.6.4 there is a reference for reset call and others
having an immediate affect or during the current evaluation phase.

Immediate notification is a source for dependence of the simulation
results on the simulator's scheduler and a basis for non parallelizable
code (e.g. in such an implementation the reset action may come after the
reset thread executes or before) . SystemC had chosen to provide
immediate notification for the user to use upon his/her responsibility.
However immediate notification should not be a 'standard' behavior of
operations provided by the kernel.

Then unless there are compelling reasons, e.g. from simulation speed
degradation, I believe that the kill and reset effects should be delayed
to the next evaluation phase.

The same should be applied to suspend (even though it becomes very close
to disable).

Regards

Yossi

From: owner-systemc-p1666-technical@eda.org
[mailto:owner-systemc-p1666-technical@eda.org] On Behalf Of
john.aynsley@doulos.com
Sent: Friday, October 01, 2010 11:15 AM
To: systemc-p1666-technical@eda.org
Subject: Draft P1666 LRM for review - updated

Folks,

I have posted an updated version of the P1666 draft LRM on

        http://www.eda.org/twiki/bin/view.cgi/P1666/WebHome
<http://www.eda.org/twiki/bin/view.cgi/P1666/WebHome>

This includes the process control extensions and sc_max_time. Just
search for "ADDITION"

Please review and provide your feedback.

You can also check the status of the plan from this same web page

John A

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