RE: [sv-cc] Meeting minutes for 03/14/2007

Well, my last message made no sense, did it?  I meant to say the empty
clauses in 1364-2005 (not 1995) that show where stuff was deprecated will
not be duplicated in the merged LRM.

Stu
~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart Sutherland
Sutherland HDL, Inc.
stuart@sutherland-hdl.com
503-692-0898
 

> -----Original Message-----
> From: owner-sv-cc@server.eda.org 
> [mailto:owner-sv-cc@server.eda.org] On Behalf Of Stuart Sutherland
> Sent: Thursday, March 15, 2007 3:38 PM
> To: 'Charlie Dawson'; 'SV-CC'
> Subject: RE: [sv-cc] Meeting minutes for 03/14/2007
> 
> > Minutes of 03/14/2007 SV-CC Meeting.
> ...
> >    - Stu has a question about VPI organization
> > 
> >      Poll of SV-CC is that we prefer the new approach.  
> Bassam wanted
> >      to know how Stu is handling the deprecated sections.
> > 
> 
> The deprecated clauses will not be duplicated in the merged 
> LRM.  They were
> only included in 1364-1995 as place holders to aid in the 
> transition from
> 1364-2001 to 1364-2005.
> 
> The PLI overview clause in the merged LRM will explicitly 
> reference the
> 1364-2001 clause and annex numbers for the deprecated PLI 
> constructs, along
> with a brief explanation of what they contain.
> 
> Stu
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> Stuart Sutherland
> Sutherland HDL, Inc.
> stuart@sutherland-hdl.com
> 503-692-0898
>  
> 
> > -----Original Message-----
> > From: owner-sv-cc@server.eda.org 
> > [mailto:owner-sv-cc@server.eda.org] On Behalf Of Charlie Dawson
> > Sent: Thursday, March 15, 2007 12:55 PM
> > To: SV-CC
> > Subject: [sv-cc] Meeting minutes for 03/14/2007
> > 
> > Minutes of 03/14/2007 SV-CC Meeting.
> > 
> > ATTENDEES
> > 000000000000000
> > 777777666666666
> > 000000111110000
> > 322111221009988
> > 221310200212131
> > 484173068517306
> > xxx-xxxxxxxxxxx Charles Dawson
> > -xxxxxxx-x-xxxx Ralph Duncan
> > xxxxxxxxxxxxxxx Jim Vellenga
> > xxxxx-xxx-x-xxx Andrzej Litwiniuk
> > x-xxxxx-xxxxxxx Abigail Moorhouse
> > -xxxx--xxxxxx-x Michael Rohleder
> > x-xxxxxxxxxxxxx Chuck Berking
> > xxxxxxxxx-xxxxx Bassam Tabbara
> > xx-xx-x-xxxxxxx Francoise Martinolle
> > xxx-xxxxxxxxxx- Ghassan Khoory
> > --xx----------- Steve Dovich
> > --xxxx----xx-xx Amit Kohli
> > 
> > 1.  Reviewed Patent information.
> > 
> >    - Chas reviewed the patent information.
> > 
> > 
> > 2.  Reviewed minutes of the 02/28/2007 Meeting.
> >      Date at the top was 02/20/2007, should be 02/28/2007.
> >      - JimV/Bassam.  ACCEPTED (unanimous) as modified
> > 
> > 
> > 3.  Liaisons
> > 
> >    - Item 890 has been completed by SV-EC.  Includes details
> >      on scheduling algorithm changes, program block semantics and
> >      clocking block semantics.  Michael already asked for
> >      a new region, which was added.  Neil asked a question
> >      back which no one responded to.  Is this a read-only
> >      region, or is it possible to schedule things are future
> >      time slots?  There never is a time when you cannot
> >      schedule something in a future timeslice.  Francoise will
> >      get back to Neil.
> > 
> >    - No other meetings to report on.
> > 
> > 
> > 4.  New business
> > 
> >    - Declare Item 1628 a duplicate of Item 741?
> > 
> >      JimV moves to declare Item 1628 a duplicate of Item 741.
> >      PASSED (unanimous)
> > 
> >    - initial values in VCD - Should we discuss?
> > 
> >      Chas to send response saying SV-CC will not work on this.
> >      Should be addressed by SV-BC.
> > 
> >    - Stu is ready for the merged data model
> > 
> >      Chas will send it on to him.
> > 
> >    - Stu has a question about VPI organization
> > 
> >      Poll of SV-CC is that we prefer the new approach.  
> Bassam wanted
> >      to know how Stu is handling the deprecated sections.
> > 
> >    - Abi's question about range iterations
> > 
> >      Should there be range transitions on the struct,
> >      union, and possibly enum, variables? Can you have
> >      packed ranges?  You can have a multiple dimension of
> >      packed structs.  Depends on the type of that you give
> >      the struct.  Francoise thinks that you cannot have a packed
> >      array of enums.  This is being worked on by Chuck in Mantis
> >      Item 1230.  Packed arrays can only be made of bit data types.
> >      So it is possible to have a packed array of packed structs.
> >      See section 5.2.  A strict interpretation would be that you
> >      cannot have enums and unions.
> > 
> >    - Others?
> > 
> > 
> > 5.  Reviewed items with proposals.
> > 
> >    - Item 1751 Clarify vpiParent for part selects
> > 
> >      Francoise asked how to spell "part-select".  Jim had it right.
> >      Bassam wanted to know how this relates to Chuck's 
> passed proposal
> >      on parents.
> > 
> >      Friendly amendment to change variable name from 'x' to 'r'.
> >      JimV/Abi.  PASSED as amended (unanimous)
> > 
> > 
> > 6.  Reviewed SV-CC items with proposals (Straw poll only).
> > 
> >    - Item 1726 Clarify meaning of vpiConstantSelect
> >      Long discussion on the relation between ranges vs 
> dynamic/static
> >      objects.  Should we limit this property to the expression in
> >      the ranges?
> > 
> >      Ran out of time.  Chas will put onto agenda for next time.
> > 
> > Motion to adjourn.  Chuck/JimV.  Meeting ended at 1:10pm.
> > 
> > 7.  Old Business
> > 
> > 8.  Action items
> > 
> >    - Ongoing review of Michael and Abi's compatibility proposal.
> >    - Francoise and Bassam to continue work on assignment patterns.
> >    - Francoise to champion adding support for typed 
> parameters to the
> >      typespec diagrams.
> >    - Abi to champion adding support for parameterized classes.
> >    - Abi/JimV to champion improving the ability to compare objects.
> >    - Steve Dovich to determine best way to deal with issues between
> >      versions of the IEEE specs.
> >    - SV-CC to review proposal for Item 0890.
> >    - Michael to compose response to the Clean Scheduling Proposal.
> >    - All to verify their Acknowledged Mantis Items.
> >    - Steve to send out exact text on referring to a prior version.
> > 
> > 9.  Items for consideration at the next meeting (they already 
> > have proposals):
> > 
> >    - Item 1726 Clarify meaning of vpiConstantSelect
> > 
> > 10. Next meeting
> >     The next SV-CC meeting will be on 03/28/2007.
> >     The next P1800 meeting will be on 04/05/2007.
> > 
> > 
> > -- 
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > 
> > 
> > 
> 
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 
> 



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