[sv-ac] RE: Call to vote: Due May 16

Hi Ed,

I uploaded a new version of the proposal with your and Erik's comments addressed: http://www.eda-stds.org/mantis/file_download.php?file_id=5022&type=bug. I deleted a sentence about accessing task static variables because IMO it makes more harm than good.

Thanks,
Dmitry

From: Eduard Cerny [mailto:Eduard.Cerny@synopsys.com]
Sent: Thursday, May 12, 2011 14:49
To: Korchemny, Dmitry; Eduard Cerny; 'sv-ac@eda-stds.org'
Subject: RE: Call to vote: Due May 16

Hi Dmitry,

please see below.

Thanks,
ed

From: Korchemny, Dmitry [mailto:dmitry.korchemny@intel.com]
Sent: Thursday, May 12, 2011 3:24 AM
To: Eduard Cerny; 'sv-ac@eda-stds.org'
Subject: RE: Call to vote: Due May 16

Hi Ed,

Please, see my comments below.

Thanks,
Dmitry

From: Eduard Cerny [mailto:Eduard.Cerny@synopsys.com]
Sent: Wednesday, May 11, 2011 23:38
To: Korchemny, Dmitry; 'sv-ac@eda-stds.org'
Subject: RE: Call to vote: Due May 16

Hello Dmitry,

here is my vote:

Mantis 3213 __X__ Yes __X__ No

http://www.eda-stds.org/mantis/view.php?id=3213
http://www.eda-stds.org/mantis/file_download.php?file_id=5003&type=bug

In 16.5.1, first item: If a variable is declared in a task, that variable is sampled as any other variable, independent of calls to the task.
You mean task calls in match items? What about variables declared in functions called in Boolean expressions? Should this line have a little more explanation?
[Korchemny, Dmitry] I copied this sentence from 16.5.2. The entire paragraph reads:

The variables that can appear in expressions shall be static design variables, function calls returning values
of types described in 16.6.1, or local variables. Static variables declared in programs, interfaces, or
clocking blocks can also be accessed. If a reference is to a static variable declared in a task, that variable is
sampled as any other variable, independent of calls to the task.

I think that it is related to any static task variable referenced in an assertion. Would it be better to just delete this statement?

[Ed:] Yes, it is like that in 15.5.2, but perhaps we should improve it. Deleting or adding more detail? I think that it is possible to refer to a function declaration and to a static variable inside it.

In For example, if a is a variable, then the value of const'(a) in the concurrent context is the current value of a.
Should it say concurrent assertion context, since concurrent context is not defined?
[Korchemny, Dmitry] Will fix.

I do not quite understand (in red)
The change (or lack of change) is determined by comparing the sampled value of the expression with the sampled value of the expression evaluated in the Postponed region of the most recent strictly prior time step in which the clocking event occurred.
Sampled value was defined as the value taken in the preponed region. Is this changing the definition for this particular case here? If not, then why to mention it since the sampled value is stable throughout the time step. If it changes the definition, then the sampled value in postponed region would reflect the changed value as a consequence of the clock tick. So, if the clock tick occurred just in the preceding time step, the current sampled value and the one from the preceding postponed region are the same. No change detected?
[Korchemny, Dmitry] Since according to the new definition the sampled value may be a current value of an expression or depend on a current value of one of its components, the sampled value may change in the simulation tick. Therefore, when we are talking about the sampled value in another tick we should point exactly where this sampled value is taken. I will add an explanation to 16.9.3 as it concerns to all sampled value functions (except for $sampled), and not only global clocking future value functions as I wrote in the proposal.

[Ed:] I think that it does need more explanation, because IMHO the statement in read sounds contradictory, confusing.
Similarly in
The other functions are defined as follows (the comparison is done between the sampled value at the invocation point and the sampled value in the Postponed region of the next tick of the global clock):

Mantis 3385 __X__ Yes ____ No

http://www.eda-stds.org/mantis/view.php?id=3385
http://www.eda-stds.org/mantis/file_download.php?file_id=4999&type=bug

Best regards,
ed
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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