[sv-cc] Meeting minutes 12/16/04

Minutes of 12/16/2004 SV-CC Meeting.

ATTENDEES

--xxxxxxxxxxxxxx Charles Dawson

xxx-xxxxxxxxxxxx Francoise Martinolle

xxxxxxxxxxxxxxxx Doug Warmke

-xxxxxxxxxxx-xxx Bassam Tabbara

-xxx-xxxxxxxxxxx Andrzej Litwiniuk

xxx--xxxxxxxxxxx Joao Geada

-xxxxxxxxxxx-xxx Jim Vellenga

xxxxxxxxxxxxxxx- Ralph Duncan

-x-x-xxxxxx--x-- Rob Slater

-x-xxxxxxxxx-x-- Sachchidananda Patel

-xxxxxxxxxxxxx-- Michael Rohleder

-xx--xxxxx-xxx-- John Stickley

xxxxxxxxxxxxx-x- Jim Garnett

xxxxxxxxxxxx--x- Steven Dovich

---x-xxxx-x-xxxx Ghassan Khoory

---------------x Swapnajit Mitra

---------------x Karen Pieper

-------------x-- Angshuman Saha

---------x------ Kevin Cameron

-------x-------- Amit Kohli

------x--------- Surrendra Dudani

x-xxx----------- Stu Sutherland

1. Reviewed Patent information.

- Francoise asked if anyone was unfamiliar with the IEEE patent rules,

and if it was needed to be read. Everyone is familiar with the patent

information. The patent information was considered read.

2. Minutes

We did not review the minutes of the previous meeting.

3. Liaisons

Karen gave us until Friday evening to resolve item 56. Then the proposal for
item

56 will be sent to the champions on Monday. The champions meet on tuesday
and

will provide recommendation for the WG meeting in January.

4. Errata with immediate priority
 
- 56
  discussion of Francoise proposal:
  Doug agrees but mentions that he would like that in the future
vpi_handle_by_name provides access to global objects in compilation units by
perhaps
specifying an auto generated name for the compilation unit or making the
compilation unit name vendor specific.
 
We agreed that this can be taken care of in a later revision as the fullname
for packages is the main concern.
 
 
Motion: Doug moves that we approve the current proposal
        Joao seconds
        no opposed, no abstain, Passes
 
- 77
Francoise would like to merge 77 with 53 since the changes mentioned in the
informal
proposal for 77 are straightforward and are touching the same diagrams as
53.
 
Charles needs to resubmit a new proposal with 53 integrating 77 changes:
   - the dotted lines for arrayvar need to be changed to solid lines.
   - the bubble ovals named reg need to be changed to logic var and the
iterations
     leading to the renamed logic var need to be labelled vpiReg
   - the bubble ovals named reg array need to be changed to array var and
the iterations
     leading to the renamed array var need to be labelled vpiRegArray.
 
Motion to subsume 77 in 53:
       Joao moves, Steve seconds
       No opposed, no abstain passes.
 
 
- 53
Francoise notices that there are still issues:
  page 3 of the pdf: need to remove paramAssign iteration from the instance
diagram.
  net array class needs to be changed to array net
  concurrent assertion needs to be changed to assertion or we need to add a
note
  for the editor that the errata fixing the assertion changes in the diagram

  needs to apply after 53 is applied.
 
- 62
We discussed the incompatibility issue arising from the merge of the 1364
reg diagram
and variables diagram to create the sv31a variables diagram. In the 1364
diagram the vpiArray property had two different meaning. In the reg diagram,
vpiArray property returning TRUE meant that the reg was an array element,
whereas in the variables diagram the vpiArray property returning true
indicated that the integer var, real var or time var
was an array. Once we merged these two diagrams, what is the meaning of
such property?
Joao said that it is more useful in the systemVerilog VPI spec to have the
property
returns whether or not a variable is an array element because we have other
ways to find
out if something is an array type (the type itself indicates if a variable
is an array or not : for ex: array var denotes a variable of data type
array, while a integer var will always be an integer variable, and for
packed arrays the value of the vpiVector property for a packed logic var
would provide the adequate answer)
 
Ralph proposed an interesting solution which is to add a new property
vpiArrayMember
with the meaning to returns true if that variable is an array member and
mark vpiArray
as deprecated.
 
Motion to add :
      vpiArrayMember property to the variables, nets and instance diagrams
      and mark vpiArray deprecated. Notes related to the vpiArray property
will have to be
      changed in all those diagrams.
      Joao moves, Ralph seconds, no opposed no abstain Passes.
 
 
A formal proposal is needed for this. TDB
 
Motion to adjourn at 1 pm
 
Received on Thu Dec 16 12:34:46 2004