I vote no on 1682. The following paragraph is still not clear: An action block of an assertion containing next value functions is performed at the time when all the next values are actually computed, that is, at the global clocking tick that follows the assertion clock tick at which the final boolean expression of the assertion is evaluated. First, the paragraph only says that the "action block" is delayed. For accuracy, it should say that the "evaluation" of the assertion is delayed as well. My suggestion: An action block of an assertion containing next value functions is performed at the global clocking tick that follows the assertion clock tick at which the final boolean expression of the assertion is evaluated. This allows the evaluation of the next value functions to be delayed until the after the next values of the signals referenced have been computed. In addition, we could add further explanation that in a simulation context, the function $future_gclk(sig) could be evaluated by the equivalent (@$gobal_clk ##1 $past_gclk(sig)) I found this sentence from the first paragraph a little cryptic and hard to follow. These functions include the capability to access the sampled value at the previous (resp. the next) global clock tick that precedes (resp. follows) immediately the timestep at which the function is called. I don't think the "resp." abbreviation is good style for a standard. How about: These functions include the capability to access the sampled value at the global clock tick that immediately precedes or follows the timestep at which the function is called. Tom John Havlicek wrote On 09/25/07 12:34 PM,: > Hi Folks: > > This is the call to vote on the proposal for 1682. > The document on Mantis is > > GlobalCLockPastNextValuefunctions1682_070912_dk.pdf > > Please vote if you are eligible. See the details below. > > J.H. > > ------------------------------------------------------------------------------ > > Ballot on Mantis 1682 > > - Called on 2007-09-25, final ballots due by 2007-10-02 T 23:59-07:00. > > > v[xxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx-xx] Doron Bustan (Intel) > v[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-x] Eduard Cerny (Synopsys) > n[---------x-xxx---------x-x-xxx-x---x] Surrendra Dudani (Synopsys) > v[xx-xxxxxxxxx-xx-xxxxx-xxx-xxx-------] Yaniv Fais (Freescale) > t[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] John Havlicek (Freescale - Chair) > v[xxxxxxxxxxxxxxxxxxrxxxxxxxxxxxxx-xxx] Dmitry Korchemny (Intel - Co-Chair) > v[xx-xxx-x--xx--xxxxx----------xx-xxxx] Manisha Kulshrestha (Mentor Graphics) > n[-----------------xxxxx-------x-xx-x-] Jiang Long (Mentor Graphics) > n[---------x--xxx.....................] Joseph Lu (Altera) > v[xxxxxx..............................] Johan Martensson (Jasper) > n[--------------x--x-xx--xx-xxxxxxx-x-] Hillel Miller (Freescale) > v[xxxxxxxxxxxxxxxxx-xxxxxxxx-xxxxxxxxx] Lisa Piper (Cadence) > v[-xxxxxxx-x-xxxxx-x..................] Erik Seligman (Intel) > v[-x--------xxxx-----xxxx-xx----------] Tej Singh (Mentor Graphics) > v[xx--xxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxx] Bassam Tabbara (Synopsys) > v[xxxxxxxxxx-xxxxxxxxxx...............] Tom Thatcher (Sun Microsystems) > |------------------------------------ attendance on 2007-09-25 > |-------------------------------------- voting eligibility for this ballot > |--------------------------------------- email ballots received > > > Legend: > x = attended > - = missed > r = represented > . = not yet a member > v = valid voter (2 out of last 3) > n = not valid voter > t = chair eligible to vote only to make or break a tie > -- ------------------ Thomas J. Thatcher Sun Microsystems ------------------ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Oct 1 13:29:25 2007
This archive was generated by hypermail 2.1.8 : Mon Oct 01 2007 - 13:29:41 PDT