[sv-bc] Notes: Feb 25 SV-BC/SV-EC 1800 Scoping Meeting

SV-BC/SV-EC 1800 Scoping Meeting
Date: Feb 25, 2015
Time: 09:00am-11:00am PST
Join online: https://meet.intel.com/matthew.r.maidment/6F695NSL
Join by Phone:
US: +1(916)356-2663
UK: +44 179340 2663
Choose bridge 5.
Conference ID: 702617185

*       Roll Call (5 min)

                2015
Rep     Company Feb 18  Feb 25
Matt Maidment   Intel   X       X
Brad Pierce     Synopsys        X       X
Ray Ryan        Mentor  X       X
Jonathan Bromley        Verilab X
Daniel Schostak ARM     X       X
Mark Hartoog    Synopsys        X       X
Neil Korpusik   Oracle  X       X
Arturo Salz     Synopsys        X
Shalom Bresticker       Intel   X       X
Dave Rich       Mentor  X
Francoise Martinolle    Cadence X       X
Stu Sutherland  SutherlandHDL   X
Sachin  Mentor  X
Brandon Tipp    Intel           X
Alex Gran       Mentor          X

*       Review Previous Meeting Notes (5 min)
      http://www.eda.org/sv-bc/hm/11692.html
      http://www.eda.org/sv-ec/hm/8568.html

      Shalom moves to approve.
      Brad seconds.
      Abstain: Alex (did not attend)
      Motion Passes.


*       Patent Policy Reminder (5 min)
      http://standards.ieee.org/board/pat/pat-slideset.ppt

        Complete.



*       Mantis Review (60 min)
      Upon review of the relevant Mantis items for a next PAR below is a summary to-date:

      Testbench:
o       Coverage: Extending/overriding/deriving covergroups
o       Constraints: Soft-constraint clarifications, Real numbers in constraint expressions
o       Other Features: Introspection, Method Overloading, Enumerations: extension/namespace

      Design/Basic:
o       Many Editorial Issues: many could be handled independently by editor and returned for bulk approval
o       Interfaces: errata, clarifications & enhancements
o       Packages: several enhancements related to parameterized & nested packages as well as separating declarations from implementations
o       Pre-processor: interest in more flexible/powerful pre-processing capabilities
o       Parameters: interaction with interfaces, subroutines, instance arrays
o       Permitting direct array slicing
o       Interop with IEEE Std 1735
o       Clarification: .*/.name, bind and libraries

*       Continue capturing overall group summary (45 min)

      From Feb 18 meeting:
*       Consensus is to include for errata and clarification.  This could include minor enhancements for resolution.  Consensus from vendors and users.
o       Would need more focused effort to build a prioritized list
o       Small errata, editorial & Clarification: as many as can be brought to the committee with proposals
*       Focus work on areas where implementations are divergent
o       AI: Matt request highlights from reflector
*       If there are major enhancements they should be done with sufficient contributors.  Asking for many enhancements to be implemented by limited number of committee members will not succeed.
*       Would like to see global resolution of priority.  During 2012 effort, BC and EC members were pulled into AC/DC work.  Would like to ensure that AC/DC or any other major initiative is properly scoped.  Should consider impact of 1801, 1802, AC, AMS/DC, 1735 and others.  (example from AC is 5068)
*       Difficult to make recommendations without timeframe.  Timeframe would influence scope.  BC/EC should suggest timeframe and factor this into their proposal (short vs medium vs long)
o       From Karen:  "I suggest making an estimate of what it will take to do the work your team feels is necessary."
o       Suggest fitting work into a 3yr delivery (2 years of tech work and 1 year of IEEE bureaucracy); Keep a prioritized list and work through it in that order until time expires-save small errata/clarification/enhancements.



      High Level Areas of Feedback
o       Real numbers in constraints
o       Interfaces - numerous issues
o       Slicing of variables/indexing arrays of interfaces
o       Coverage
o       Package extensions
o       Enumerates
o       Divergence: method chaining (also everyday annoyance)
o       Libraries/binds/interface/package interaction not well defined

        Areas that would need a champion/driver to push through
o       Introspection
o       Enumerate extensions/namespace
o       Randomization of real values  (using them as state values is smaller scope)
o       Method overloading
o       Unconstrained array/variable size expressions (anti-Gord :))
o       Package changes
o       Interface issues - esp beyond minor errata/clarification (potentially Mark Hartoog+Jonathan Bromley)

Concurrent assertions in classes not high on SV-EC/BC feedback list; would be a big drain to BC/EC if pursued by 1800WG.

Interfaces are a day-to-day frustration and source of implementation divergence.

AI: Matt to post drafts of presentation to 1800WG to reflector
AI: All close on details of the presentation via the reflector



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.