RE: [sv-ac] Minutes of SV-AC meeting 3/8/2011

But the minutes should reflect the current status.
Dmitry

From: ben cohen [mailto:hdlcohen@gmail.com]
Sent: Thursday, March 10, 2011 00:53
To: Korchemny, Dmitry
Cc: thomas.thatcher@oracle.com; sv-ac@eda.org
Subject: Re: [sv-ac] Minutes of SV-AC meeting 3/8/2011

but they can pass their opinions though.
Ben
2011/3/9 Korchemny, Dmitry <dmitry.korchemny@intel.com<mailto:dmitry.korchemny@intel.com>>
Hi Tom,

It looks to me that Dana and Srini are not valid voters.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@eda.org<mailto:owner-sv-ac@eda.org> [mailto:owner-sv-ac@eda.org<mailto:owner-sv-ac@eda.org>] On Behalf Of Thomas J Thatcher
Sent: Wednesday, March 09, 2011 01:28
To: sv-ac@eda.org<mailto:sv-ac@eda.org>
Subject: [sv-ac] Minutes of SV-AC meeting 3/8/2011

Minutes of SV-AC Meeting
Date: 2011-02-22
Time: 16:30 UTC (8:30 PST)
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=6362971

Agenda:
-------
- Reminder of IEEE patent policy.
See: http://standards.ieee.org/board/pat/pat-slideset.ppt

- Minutes approval

- F2F update

- Email ballot results
2476 : Need clarification about system functions $onehot, etc
Passed with friendly amendments

2804: Failed.

- New issues

- Issue resolution/discussion
3376: triggered should be typeset as code

- Enhancement progress update

- 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[xx-xxx...........................] Ashok Bhatt (Cadence)
  v[xxxxxx-xxx-xxxxxxxxx-x-xxxxx--xxx] Laurence Bisht (Intel)
  v[xxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxx-] Eduard Cerny (Synopsys)
  v[-xx---xxx--x-xxxxxxx-xxxxx-xxxxxx] Ben Cohen
  n[--------------xx-x-xxx-x--xxxxxxx] Surrendra Dudani (Synopsys)
  v[-x-x----x-x-x--xx---xxxx---x-xxxx] Dana Fisman (Synopsys)
  n[------------xxxxx-xxxx-x-xxxxxxxx] John Havlicek (Freescale)
  v[xxxxxxxxxxxxxxxx-xxx-xxxxxxxxxxxx] Tapan Kapoor (Cadence)
  n[x-x..............................] Jacob Katz (Intel)
  t[xxxxxxxxxxxxxxxx--xxxxxxxxxxxxxxx] Dmitry Korchemny (Intel ¿ Chair)
  v[-xxxxxxxxxxxxxxx--xxxxxx-xxxxxxxx] Scott Little (Freescale)
  v[xxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxx] Manisha Kulshrestha (Mentor
Graphics)
  v[xxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxx] Anupam Prabhakar (Mentor Graphics)
  v[xxx-xxx--x-xx-xxx-xx--xxxxxxx-xxx] Erik Seligman (Intel)
  v[-x-xxx-xxxx-xxxx--xxxxxx-xxxxxxx.] Samik Sengupta (Synopsys)
  v[xxxxxxxxxxxxxxx-xxxxxxxxxxxxx-xxx] Tom Thatcher (Oracle ¿ Co-Chair)
  v[--xx-------x.....................] Srini Venkataramanan (CVC Pvt Ltd)
    |- attendance on 2011-03-08
  |--- voting eligibility on 2011-03-08

Minutes:
--------

- Reminder of IEEE patent policy.
See: http://standards.ieee.org/board/pat/pat-slideset.ppt

Participants were reminded of the patent policy.

- Minutes approval
Erik: Move to approve minutes
Tom: Second
       Vote results: 8y, 0n, 0a

- Email ballot results
2476 : Need clarification about system functions $onehot, etc
Passed with friendly amendments

Erik: Scott's comment: 2'b1 should be replaced with 2'b01
       Other comment: $isunknown was not defied in terms of $countbits.
Erik: Will make the changes.

2804: Failed.
Ed: If you have an event variable, you can't write posedge <var>
       Condition 2 only required for the "posedge var" form.
Erik: Will make changes.
Manisha: Suggest: just say "if the event expression is of the form
       <edge_expression> variable, then the variable should not appear in the
       body of the procedure"

- Issue resolution/discussion
3376: triggered should be typeset as code
(Jacob joined)
Dmitry: Has uploaded a proposal which simply changes the typsetting of the
       word "triggered" to courier.
Erik: Move to approve proposal
Manisha: Second
       Vote results: 8y, 0n, 0a

- F2F update
Dmitry: Summarizing the face-to-face meeting.
       Most difficult issue was continuous assignments in checkers

       Another issue discussed was checker sampling
manisha: In 2009 std, checker variables not sampled.
       There are some cases where there would be backward incompatibilites.
       i.e. a checker variable on the rhs of a non-blocking assignment.
       However, the end result would be the same.

- Enhancements progress update
Manisha: Mantis 3295 Assertion control system tasks
       Updated proposal in response to Shalom's comments.
       Defined a new function $assertcontrol()
Anupam: We are still keeping the legacy $asserton function, correct?
Manisha: Yes
       Tom and Anupam will review the proposal

Defining triggered method for sequence arguments
Can we allow a sequence method on formal arguments

i.e.
property p (sequence s);
       s.triggered;
endproperty

Mantis 3191
Jacob: It's not legal to call triggered method on sequence s. (because of
       substitution semantics?). Could we do a smaller extention to allow
       only this case?
       A more comprehensive proposal would be to allow calling the triggered
       method on any sequence expression.

3191: Anupam and Erik will review this proposal

3069: Global Clocking
    Ed and Manisha will review
case?

Meeting adjourned.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.