SV-AC_Minutes_2011_07_19 < P1800

P1800 Web>SystemVerilogAssertionCommittee>SVACMeetingMinutes>SV-AC_Minutes_2011_07_19 (2011-07-19, ErikSeligman) (raw view)EditAttach
Minutes of SV-AC Meeting

Date: 2011-07-19

Time: 16:00 UTC (9:00 PDT)

Duration: 1.5 hours

Dial-in information:

--------------------

Meeting ID:            38198

Phone Number(s):

1-888-813-5316         Toll Free within North America

Live Meeting:

[[https://webjoin.intel.com/?passcode=2618319]]

Agenda:

-------

- Reminder of IEEE patent policy.

See: http://standards.ieee.org/board/pat/pat-slideset.ppt

- Minutes approval

- Email ballot results:

Issues 2476 and 3113 passed: 10y/0n/0a.

Issue 3015 passed with friendly amendments: 10y/0n/0a.

- Champions Feedback

3135: Verbal explanation of nexttime and always is misleading for multiple clocks. (Dana)

           Friendly Amendment: Font Problem

- New issues

3672: hierarchical access to named block in assertion action blocks

- Issue resolution/discussion

3033: Allow procedural control statements is checkers

- Enhancement progress update

3206: Deferred assertions are sensitive to glitches

- Opens

Attendance Record:

------------------

         Legend:

                 x = attended

                 - = missed

                 r = represented

                 . = not yet a member

                 v = valid voter (2 out of last 3 or 3/4 overall)

                 n = not a valid voter

                 t = chair eligible to vote only to make or break a tie

Attendance re-initialized on 2010-07-06:

  n[x--xxx---xxxx-xxx-xxx...........................] Ashok Bhatt (Cadence)

  v[xxx-xxxxxx-xxxxxxxxxx-xxx-xxxxxxxxx-x-xxxxx--xxx] Laurence Bisht

(Intel)

  v[xxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxx-] Eduard Cerny

(Synopsys)

  v[xxxxxxxx--------xx---xxx--x-xxxxxxx-xxxxx-xxxxxx] Ben Cohen (Accellera)

  n[-----------------------------xx-x-xxx-x--xxxxxxx] Surrendra Dudani

(Synopsys)

  v[x-xxxxxx........................................] Shaun Feng

(Freescale)

  v[--x-x--x-x-xxxx-x-x----x-x-x--xx---xxxx---x-xxxx] Dana Fisman

(Synopsys)

  n[---------------------------xxxxx-xxxx-x-xxxxxxxx] John Havlicek

(Freescale)

  v[-x-xxx-xx-xxxx-xxxxxxxxxxxxxxxx-xxx-xxxxxxxxxxxx] Tapan Kapoor

(Cadence)

  v[-xx-xxxxx-xxxx-x-x..............................] Jacob Katz (Intel)

  t[xx--xxx-xxxxxxxxxxxxxxxxxxxxxxx--xxxxxxxxxxxxxxx] Dmitry Korchemny (Intel ¿ Chair)

  v[xxxx-xxxxx-xxxx-xxxxxxxxxxxxxxx--xxxxxx-xxxxxxxx] Scott Little

(Freescale)

  v[xxxxxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxx] Manisha Kulshrestha (Mentor Graphics)

  v[xxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxx] Anupam Prabhakar (Mentor Graphics)

  v[xxxx--xxx-xxxx-xxx-xxx--x-xx-xxx-xx--xxxxxxx-xxx] Erik Seligman (Intel)

  v[xxxx-xxxxxxxxxx-x-xxx-xxxx-xxxx--xxxxxx-xxxxxxx.] Samik Sengupta

(Synopsys)

  v[xxxxxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxxxxxx-xxx] Tom Thatcher (Oracle ¿ Co-Chair)

  n[------------xx---xx-------x.....................] Srini Venkataramanan (CVC Pvt Ltd)

  n[--x.............................................] Vibarajan Viswanathan (Marvell)

    |- attendance on 2011-07-12

  |--- voting eligibility on 2011-07-12

Minutes

-------

- Reminder of IEEE patent policy.

See: http://standards.ieee.org/board/pat/pat-slideset.ppt

Participants were reminded of the IEEE patent policy.

- Minutes approval

Eric: Move to approve minutes

Scott:     Second

           Vote results: 9y, 0n, 0a

- Email ballot results:

Issues 2476 and 3113 passed: 10y/0n/0a.

Issue 3015 passed with friendly amendments: 10y/0n/0a.

(Manisha joined)

Erik: Dmitry asked whether Shalom's comment was addressed in this

     proposal. Erik did add a sentence specifying where these functions

     may be called.

Dmitry:    What about different types of constant and non-constant values.

     Suggest that these new functions may be used anywhere pure functions

     are used.

Erik: Looking for comparable example in LRM. Most functions, the LRM

     doesn't say where they can or can't be used.

Dmitry:    In 20.5 the text says that "this function may be used in constant

     expressions. Think text for this proposal should be the same.

Tom: Suggest . . ., including constant functions

Erik: Will make that change, and will voice vote later in the meeting.

3015: A proposal was uploaded to address the friendly amendments

Tom: Looks good to me.

Tom: Move to approve proposal

Erik: Second

           Vote results: 10y, 0n, 0a

Back to 2476: Erik uploaded the modified proposal

Erik: Move to approve

Scott:     Second

           Vote results: 10y, 0n, 0a

- New issues

3672: Hierarchical access to named block in assertion action blocks

Ed:  It's not specified what the access path to variables declared in

     the action block.

     Should the hierarchical path include the assertion label?

     Should it include the block label?

Dmitry:    It should be consistent with immediate assertions

Ed   But what is th the access path for immediate assertions?

Dmitry:    Think that immediate is equivalent to "if" An "if" statement

     doesn't create a block hierarchy, so hierarchy shouldn't include

     assertion label.

Ed:  Shouldn't assertion label be part of the access path to variable?

Dmitry:    Example

     cover property (. . . ) begin : cnt_blk logic cnt; cnt = cnt +1; end

     does this count

Ed:  Don't think so. Locally defined variable is created each time.

Manisha: Assertion action block is a statement. If you create a block,

    it seems that it would be a static block.

Ed:  What is the access path to variable?

Manisha: When you use %m in $error in an action block, it will print the

     path to the action block including the assertion label.

     Section 16.3:

     "The optional statement label (identifier and colon) creates a named

     block around the assertion statement (or any other statement) and the

     hierarchical name of the scope can be displayed using the %m format

     specification."

- Champions Feedback

3135: Verbal explanation of nexttime and always is misleading for multiple

     clocks. (Dana)

           Friendly Amendment: Font Problem

Erik: Able to open proposal. Will fix the font problems.

- Issue resolution/discussion

3033: Allow procedural control statements in checkers

Dmitry:    Addressed comments from last time.

     Changed examples from "always" to "always_ff"

     Added tasks in checkers.

     Suggest review of proposal

Tom, Manisha will review it.

Meeting adjourned
Topic revision: r1 - 2011-07-19 - 21:47:21 - ErikSeligman
P1800