RE: [sv-ac] FW: P1800 AC issues

Hi All,

I think the sampling rules should be based on the signal/variable being
referenced rather than where the property/sequence lives. So,
if a property/sequence is not in the clocking block but is refering
to a signal (hierarchically) which is in the clocking block, then 
the sampling of that signal will happen based on the clocking block
and it will be independent of sampling of other signals in that
property/sequence. 

Now, the issue is how to handle signals in a property/sequence 
which are getting sampled differently ? Should it be allowed as it 
might create undesirable results ? 

Even if we make sampling based on location of property/sequence/assertion,
the above question remains as all the variables used in the property/squence
may not be inputs/outputs of the clocking block.

Another question is about #0 sampling in clocking block. In case of #0
sampling, the inputs are supposed to get sampled in Observe region and
properties also get evaluated in Observe region. So, which one happens
first or is it a race ? Currently LRM does not clarify it.


Thanks.
Manisha


#241: I think there is some "mixup" here by author about sampling and
scheduling (within timestep). The question is really about sampling and I am
not sure what Ed/Surrendra are trying to say. Seems to me a clarification in
the LRM here would be to say that the *default* input skew for properties is
#1step same as clocking block default. If an assertion/property/sequence
lives in a clocking block it would follow whatever input skew sampling is
defined there for the inputs (and default is #1step in a clocking block).
Meaning if a property is not inside a clocking block it is inside a
"virtual" one with #1step. That's really it I think, no double resampling
and what not.