Hi Tom,
The resolution was to change the name of 3033 to "Enhance checker modeling capabilities".
Thanks,
Dmitry
-----Original Message-----
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Thomas J Thatcher
Sent: Tuesday, October 11, 2011 19:38
To: sv-ac@eda.org
Subject: [sv-ac] Minutes of SV-AC Meeting 10/11/2011
Date: 2011-11-10
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=7291077
Agenda:
-------
- Reminder of IEEE patent policy.
See: http://standards.ieee.org/board/pat/pat-slideset.ppt
- Minutes approval
- Champions' feedback
3213: Update definition of sampled value
2093: Checker construct should permit output arguments
3034: Allow continuous and blocking assignments in checkers
- 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-xxxxx-xxx--xxx---xxxx-xxx-xxx...........................] Ashok Bhatt (Cadence)
n[-------xx--xxx-xxxxxx-xxxxxxxxxx-xxx-xxxxxxxxx-x-xxxxx--xxx]
Laurence Bisht (Intel)
v[xxx-xxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxx-] Eduard Cerny (Synopsys)
v[xxxxxxx-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[xxxx---------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[-xxxxxxxx---x-xxx-xx-xxxx-xxxxxxxxxxxxxxxx-xxx-xxxxxxxxxxxx] Tapan Kapoor (Cadence)
v[-xx-xxx---x-xx-xxxxx-xxxx-x-x..............................] Jacob Katz (Intel)
t[xxx-xxxxxxxxx--xxx-xxxxxxxxxxxxxxxxxxxxxxx--xxxxxxxxxxxxxxx] Dmitry Korchemny (Intel ¿ Chair)
v[xxx-xxxxxxxxxxx-xxxxx-xxxx-xxxxxxxxxxxxxxx--xxxxxx-xxxxxxxx] Scott Little (Freescale)
v[-xxxxx-xxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxx]
Manisha Kulshrestha (Mentor Graphics)
v[xx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxx] Anupam Prabhakar (Mentor Graphics)
v[xxxxx-xxxxxxxxx--xxx-xxxx-xxx-xxx--x-xx-xxx-xx--xxxxxxx-xxx] Erik Seligman (Intel)
v[xxxx-xxxxx-xxxx-xxxxxxxxxx-x-xxx-xxxx-xxxx--xxxxxx-xxxxxxx.] Samik Sengupta (Synopsys)
v[xxxxxxxxx-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-10-11
|--- voting eligibility on 2011-10-11
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 minutes
Erik: Second
Vote results: 8y, 0n, 0a
- Champions' feedback
3213: Update definition of sampled value
Anupam: Move to accept proposal
Erik: Second
Vote results: 8y, 0n, 0a
2093: Checker construct should permit output arguments
Brad's Objection:i Why doesn't the proposal permit untyped output arguments?
Dmitry: Why did we restrict output arguments?
Tom: It seemed strange to allow an untyped output argumet, because the
checker is the one assigning to it.
Anupam: Output arguments have a continuous assignment semantic, while
input arguments have a substitution semantic.
Dmitry's example: On case where untyped output argumets might make sense:
checker check (input untyped a, output untyped b);
assign b = a;
endchecker
Dmitry: untyped argument would permit output sequences, which
Dmitry: Main issue is that we don't have time to explore ramifications of
untyped output arguments.
Anupam: If we allowed untyped arguments, we could not have continuous
assignment semantics for outputs.
Dmitry: No, we could.
Anupam: We would need to think about this.
Ben: We should keep it simple.
Dmitry: Will modify proposal by writing more justification for the no
untyped output arguments restriction.
Brad's next comment: Why "In a similar manner to sequences & properties"
Scott: Is there anything special about sequence & property default values?
Function and task arguments may also have default values.
Dmitry: No, this is important.
Scott: Sequences & properties do allow untyped arugments, which are not
allowed in tasks & functions. Therefore Seq, Prop & checkers do
have special rules.
3034: Allow continuous and blocking assignments in checkers
Shalom's friendly amendment: Need to expand summary of Mantis 3033 to
include the functionality of 3034.
Ed: Move to change summary field of 3033 in Mantis to
"Enhanced checker modeling capability"
Ben: Second
vote results 86, 0n, 0a
- Opens
Will meet next week if we get additional feedback from the Champions.
-- 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.Received on Wed Oct 12 05:00:19 2011
This archive was generated by hypermail 2.1.8 : Wed Oct 12 2011 - 05:00:23 PDT