SV-AC_Minutes_2011_09_20 < P1800

P1800 Web>SystemVerilogAssertionCommittee>SVACMeetingMinutes>SV-AC_Minutes_2011_09_20 (2011-09-21, ErikSeligman) (raw view)EditAttach
Minutes of SV-AC Meeting

Date: 2011-09-20

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

Duration: 2 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=3598654]]

Agenda:

-------

- Reminder of IEEE patent policy.

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

- Minutes approval

- Email ballot results:

Issue 2093 failed: 7y/1n/0a.

- New issues

3766: 17.6 : Error in use of variable in example

3564: Sec 9.2.2.2.1 needs to clarify whether variables read in an

    assertion contribute to the sensitivity of an always_comb

- Champions' feedback

3069      Relax rules for $global_clock resolution

- Issue resolution/discussion

3145: Need to clearly define "maximal property"

- 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:

  v[-xxxxx-xxx--xxx---xxxx-xxx-xxx...........................] Ashok Bhatt (Cadence)

  n[-----xx--xxx-xxxxxx-xxxxxxxxxx-xxx-xxxxxxxxx-x-xxxxx--xxx] Laurence Bisht (Intel)

  v[x-xxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxx-] Eduard Cerny (Synopsys)

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

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

Surrendra Dudani (Synopsys)

  n[---------x-xxxxxx........................................] Shaun Feng (Freescale)

  v[xx---------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[xxxxxxx---x-xxx-xx-xxxx-xxxxxxxxxxxxxxxx-xxx-xxxxxxxxxxxx] Tapan Kapoor (Cadence)

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

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

  v[x-xxxxxxxxxxx-xxxxx-xxxx-xxxxxxxxxxxxxxx--xxxxxx-xxxxxxxx] Scott Little (Freescale)

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

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

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

  v[xx-xxxxx-xxxx-xxxxxxxxxx-x-xxx-xxxx-xxxx--xxxxxx-xxxxxxx.] Samik Sengupta (Synopsys)

  v[xxxxxxx-xxxxxxxxxxxxx-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-09-20

  |--- voting eligibility on 2011-09-20

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

Ben: : Move to approve meeting minutes

Erik : Second

     Vote Results: 10y, 0n, 0a

- Email ballot results:

2093: Checker construct should permit output arguments

     Failed: 1 no vote

Manisha: Rules for inferring data type need fixing as they are still

     in

Erik: This will not be backward incompatible.

Dmitry:    

Scott:     Does this mean I can't have untyped input ports if I have an

     output port

Dmitry:    Examples

     checker check(a,b,c);                    Legal

    checker check(a,b, output bit c);        Legal

     checker check(input a, b, output bit c); Illegal

Scott:     In last paragraph, what does check refer to.

Tom: Suggest just removing the word "check" from sentence.

Dmitry:    Will upload latest version

Dmitry: Uploaded new version which addressed all no votes and friendly

     amendments.

Erik: Move to approve 2093

Ben: Second:

     Vote results: 10y, 0n, 0a

- New issues

3766: 17.6 : Error in use of variable in example

Dmitry:    This is an editorial issue: Only an underscore is inserted into the

     variable name in the example. No need to take a vote.

3564: Sec 9.2.2.2.1 needs to clarify whether variables read in an assertion contribute to the sensitivity of an always_comb

Manisha

Dmitry:    What about variables that appear in action block?

Manisha:   There are two types of action blocks: concurrent assertions

           and immediate assertions.

Erik: Proposal says action block triggered by sampled values: When

     will this trigger the always block.

Tom: Triggering always block with sampled values is strange.

     On a posedge clock, p, q change, but the sampled value

     doesn't change until next cycle. On the next cycle the

     always_comb is triggered, but assertion will not evalueate

     because it is not

Dmitry:    More appropriate to say that the clock triggering the concurrent

     assertion is added to the sensitivity list Manisha

Dmitry:    Always_latch

Erik: Always latch is the same as always_comb.

(Tom left the meeting at this point)

    *    Need to understand what should be defined with always @*. It is

similar

     to always_comb, but not identical.

    *     There are also different corner cases that should be carefully

described

     even for always_comb for assertion action blocks.

    *     It is not feasible to completely handle this issue at the

remaining time.

    *     The Mantis may be split into two: one clarifying the basic case,

and the

     other - a general one, also all corner cases.

    *     Manisha will send the updated basic proposal in the next couple

of days,

     and Dmitry will call to vote.

3069: Relax rules for $global_clock resolution

SV-BC feedback backed up SV-AC solution with introduction of the backward incompatibility. The alternative solution that SV-BC pointed out was to introduce a local clocking in addition to global clocking.

3145: : Need to clearly define "maximal property"

We will have an email discussion, and then will decide about it at the next meeting.

Meeting adjourned.
Topic revision: r1 - 2011-09-21 - 15:20:58 - ErikSeligman
P1800