Date: Mon Jul 23 2012 - 00:06:18 PDT
Hi Dave,
Here are my votes"
4144 - Abstain. The calculations are correct now but the explanation is out of proportion. LRM is not a Probability manual.
3659 - No. In the LRM the examples should be unambiguous. Instead of saying "If bin g12_15 is declared as an array bin using []"need to provide a complete a complete bin definition, such as:
wildcard bins g12_15_array[] = ...
The same comment is applicable to the second example, too.
4252 - Yes
4129 - Yes with the following friendly amendment: '&&' and '||' should be bold.
3474 - Yes.
Friendly amendment: Change the font of expect, unique, unique0, and priority where they are typeset bold Times New Roman 10 in the text (not in the table) to bold Courier New 9.
3030 - Yes to be left unresolved
3032 - Yes to be left unresolved
2182 - Abstain (to be left unresolved)
The situation is not acceptable that the construct introduced in 2009 does not have VPI for six years since its introduction. However, it is not reasonable to delay the standard issue for several more months because of this.
Thanks,
Dmitry
From: owner-sv-xc@eda.org [mailto:owner-sv-xc@eda.org] On Behalf Of Rich, Dave
Sent: Tuesday, July 17, 2012 10:20
To: sv-xc@eda.org
Subject: E-mail vote due 7/23
This e-mail vote is due Monday July 23 at 8:00am PDT, one hour before our next scheduled meeting. This e-mail vote represents all remaining unresolved ballot comments. If I have missed any, please let me know. The WG asked that 4252 be added to the list of LRM changes to the next draft
The following have proposals ready to be reviewed.
ID<http://www.eda-twiki.org/svdb/view_all_set.php?sort=id&dir=DESC&type=2&print=1>
Category<http://www.eda-twiki.org/svdb/view_all_set.php?sort=category&dir=DESC&type=2&print=1>
Summary<http://www.eda-twiki.org/svdb/view_all_set.php?sort=summary&dir=DESC&type=2&print=1>
0004144<http://www.eda-twiki.org/svdb/view.php?id=4144>
SV-EC
2012 Ballot comments 16 & 17. Probability in 18.5.10 not correct
0003659<http://www.eda-twiki.org/svdb/view.php?id=3659>
SV-EC
2012 Ballot comment 25: Wildcard bin expansion/naming mechanism
0004252<http://www.eda-twiki.org/svdb/view.php?id=4252>
SV-AC
Inconsistency related to use of automatic variables in sampled value functions
0004129<http://www.eda-twiki.org/svdb/view.php?id=4129>
SV-EC
2012 Ballot comment 50: Need to clarify ambiguous binding of matches operator
0003030<http://www.eda-twiki.org/svdb/view.php?id=3030>
SV-AC
2012 Ballot comment 45: Allow checker instantiation in functions and tasks
0003474<http://www.eda-twiki.org/svdb/view.php?id=3474>
SV-AC
2012 Ballot comment 54: Extend assertion control to apply to 'violation reports' for unique/priority case
The WG asked that we vote on the following issues to be left unresolved in the current PAR standard. The WG will provide the appropriate ballot responses as required by the IEEE. The subcommittees may continue to work on any unresolved issues for the next PAR, including drafting proposals; they just can't take any binding votes.
ID<http://www.eda-twiki.org/svdb/view_all_set.php?sort=id&dir=DESC&type=2&print=1>
Category<http://www.eda-twiki.org/svdb/view_all_set.php?sort=category&dir=DESC&type=2&print=1>
Summary<http://www.eda-twiki.org/svdb/view_all_set.php?sort=summary&dir=DESC&type=2&print=1>
0003030<http://www.eda-twiki.org/svdb/view.php?id=3030>
SV-AC
2012 Ballot comment 45: Allow checker instantiation in functions and tasks
0003032<http://www.eda-twiki.org/svdb/view.php?id=3032>
SV-AC
2012 Ballot comment 44: Allow forcing in checkers
0002182<http://www.eda-twiki.org/svdb/view.php?id=2182>
SV-CC
2012 Ballot comment 56: Elaborate VPI diagrams for checkers
Thank you all for your time and effort. If we can get all these issues resolved by the meeting on the 23rd, it will be our last meeting.
Dave Rich
Verification Technologist
Mentor Graphics Corporation
[Description: Description: Twitter-32]<http://www.twitter.com/dave_59>[Description: Description: Technorati-32]<http://go.mentor.com/drich>
---------------------------------------------------------------------
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.
