Re: [sv-ec] Clocking Blocks and #0 Semantics

From: <jonathan.bromley_at_.....>
Date: Mon Sep 22 2008 - 23:39:13 PDT
Gord, sorry, I didn't properly acknowledge this in my 
previous reply:

> Hmmm - if you write your TB as a module I think the above is
> correct in the sense that the TB can see the old (preponed)
> value of the input clockvar versus a new value computed
> by the DUT.  If the TB is a program then the TB should be scheduled
> in the re-active region and the input clockvars should have
> already been updated.  But is that really a "race"?

You're right, it's not a race - if a module TB waits on the
real clock event rather than the clocking block's event,
then it will reliably read input clockvars before they
have been updated by the clocking block - in other words,
it will get the previous clock's sample. 
-- 
Jonathan Bromley


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Sep 22 23:44:32 2008

This archive was generated by hypermail 2.1.8 : Mon Sep 22 2008 - 23:45:12 PDT