Minutes of 12/01/2004 SV-CC Meeting.
ATTENDEES
0000000000000
4444444444444
1111111110000
2111100009999
0211022102211
1470360369250
xxxxxxxxxxxxx Charles Dawson
-xxxxxxxxxxxx Francoise Martinolle
xxxxxxxxxxxxx Doug Warmke
xxxxxxxxx-xxx Bassam Tabbara
x-xxxxxxxxxxx Andrzej Litwiniuk
--xxxxxxxxxxx Joao Geada
xxxxxxxxx-xxx Jim Vellenga
xxxxxxxxxxxx- Ralph Duncan
x-xxxxxx--x-- Rob Slater
xxxxxxxxx-x-- Sachchidananda Patel
xxxxxxxxxxx-- Michael Rohleder
--xxxxx-xxx-- John Stickley
xxxxxxxxxx-x- Jim Garnett
xxxxxxxxx--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
xx----------- Stu Sutherland
1. Reviewed Patent information.
- Charles Dawson read the patent information.
2. Reviewed minutes of the 11/24/04 Meeting.
- Doug pointed out that for Item 288, the structure referred to as
"uint_32_t" is actually "uint32_t".
- Jim commented that it was unclear if Item 201 had been passed.
The minutes do not record votes on friendly amendments, only
the final votes on items and motions. Item 201 DID pass.
- Doug/Ralph. Minutes accepted as amended.
3. Liaisons
- Encryption has accepted the current draft. That will have some
significant impact on VPI. This probably will not be addressable
in this round of the draft, Steve will see about making a proposal
to the SV-CC committee.
- No other meetings were reported on.
4. New business
- Items 41, 51, 169
Brad had sent email indicating that the SV-CC did not need to be
concerned with these, so the issue was dropped.
- Item 45 - Should it be "Immediate"?
Jim thinks there's no hope of addressing today. Motion to remove the
Immediate tag. Jim/Ralph. ACCEPTED (unanimous)
- Review all remaining items which do not have a proposal and are marked
as "Immediate". By my count, there are at most 19 such Items.
- Remove tag from 57?
JimV/Sachi. ACCEPTED (unanimous)
- Move to ask P1800 for more time to resolve 53-56, 62, and 77.
Doug/Steve. ACCEPTED (unanimous)
- The rest have proposals.
5. Reviewed of items with proposals.
- Item 265 sv_vpi_user.h has redundancy
Friendly amendment on instance diagram to remove concurrent assertion.
JimV/Bassam PASSED (unanimous) as amended
Bassam will update.
- Item 313 PTF 296: Generate stmts will need change made in VPI
JimV/Ralph. PASSED (unanimous)
- Item 307 PTF 530: 26.6.17: expr class does not contain vpiTchkTerm - should model different
JimV/Ralph. PASSED (unanimous)
- Item 318 Utility fn to reveal if packed type actual form == canonical form
Doug/Michael. PASSED (unanimous)
- Item 309 PTF 622: Return value for left/right range of unsize parameter
JimV/Steve. PASSED (unanimous)
- Item 278 contradiction between example 3 in E.9.4 and specification for packed arrays embedded in aggregates
Steve/JimV. PASSED (unanimous)
- Item 301 Is every unpacked array a VPI array var?
Michael/Steve. PASSED (unanimous)
- Item 160 multiple packed array dimensions (E.6.6, E.10.1 differences)
JimV tried out example to make sure it works.
Doug/JimV. PASSED (unanimous)
- Item 292 vpi_handle_by_multi_index return types
JimV/JimG. PASSED (unanimous)
- Item 293 Clean up vpiWaiting/Process typo
Ralph/JimV. PASSED (unanimous)
- Item 289 In VPI model, "mod port" should be one word
JimV/Doug. PASSED (unanimous)
- Item 061 Meaning of vpiMultiArray depends on 1364 but is in conflict with it
JimV/Michael. PASSED (unanimous)
- Item 049 Necessity of specifying import fn return type
Doug/JimG. PASSED (unanimous)
- Item 267 VPI model for randcase statements (section 12.15)
JimV/Ralph. PASSED (unanimous)
- Item 005 Compatibility of Section E.6.7 of SV3.1A with IEEE PLI aval and bval
JimV/Michael. PASSED (unanimous)
- Item 064 Note 20 of section 31.10 is unclear
Ralph/JimV. PASSED (unanimous)
- Item 063 Conflicts in notes 2. 4. and 11 of section 31.10
Friendly amendment to change "30.10" to "31.10".
JimV/Ralph. PASSED (unanimous) as amended
- Item 158 Restructure sv_vpi_user.h to partition the VPI in a more logical form
Steve thinks that we need to insist the the working group accept changes after
the deadline in the include file. We need to do a careful review of the include
file.
"type spec" should be "typespec".
Remove "/* NOTE: Object value range re-started at 600 ... */" comment.
Move vpiNullConst through vpiDistType to after vpiVisibility (and it's values).
JimV/Steve. PASSED (unanimous) as amended
Michael to update
- Item 330 Amend errata 0000205 in light of 0000288
Steve/Ralph. PASSED (unanimous)
Michael will add PDF or HTML version of the proposal.
- Item 052 vpiFuncType return values for systemVerilog datatypes
JimV asked if the function diagram have a link to the typespec class?
Sachi says that no, but he could add it. JimV thinks that should be a separate
errata. Should we put this into vpi_user.h in 1364, even though it is really
for 1800?
JimV/Ralph.
Chas thought that the proposal was a bit of a cop out. Jim thought maybe we should
try to come up with a more effective solution.
Motioned withdrawn.
Sachi to drive finding a better solution.
- Item 311 PTF 329: 27.29: vpi_put_data not used in example
Steve/JimG. PASSED (unanimous)
- Item 310 PTF 623: 26.6.15 should not be modeled with multiple labels on one transition
Chas neglected to add appropriate colors to the proposal.
Steve/JimV. PASSED (unanimous)
Chas to add colors.
- Item 040 diagram for parameter is missing
Chas neglected to add appropriate colors to the proposal.
This handles any parameter that has a type, but not one where a parameter is a type.
JimV to add a second Item to deal with remaining issue.
JimV/Doug. PASSED (unanimous)
Chas to add colors.
- Item 312 PTF 368: 26.3.3 Should vpiLineNo and vpiFile apply to generate objs?
Steve noted that the template says SystemVerilog 3.1, which is wrong for this
1364 issue. Chas noted that all his proposals use the template.
Steve/JimG. PASSED (JimV abstained)
- Item 308 PTF 605: describe better which condifion trigger action callbacks
Steve/JimG. PASSED (unanimous)
6. Old Business
SV-CC action items:
- Francoise to ask Peter Ashenden what was done to improve
printing from Rational Rose.
- Francoise to inquire about the feasibility of third parties
shipping the UML for the diagrams.
- Joao/Francoise to file SV-BC item asking to define linearization.
Passed 160 instead.
- Francoise to check with SV-BC on default return type of functions.
Passed 49 instead.
- Chas to ask Karen about updating the diagrams (does not fit well
with approved process).
We have working model now.
- Andrzej to make sure the LRM says that for the C layer of DPI,
representations of a type are always the same regardless of where
it is (packed struct, member of array, ...etc.).
Previously discussed.
- Francoise and Bassam to reconcile sections 28 and 31.
Covered by 265.
- Everyone to review outstanding items to make sure high priority ones
are resolved prior to 12/1/2004
Done.
- Doug to update Item 201.
Done.
- Michael to update Item 288.
Done.
- Chas to update Item 303.
Done.
- Francoise and Chas to review Item 265's proposal.
Done.
- Stu to see if older versions of IEEE standards are still available.
Stu checked and they are still available.
PTF action items:
- Steve to compare BNF with the access available
for attributes to see if they match
- Francoise to remove "+" from tags in UML diagrams and
add vpi prefix where appropriate.
- Francoise to send out HTML for 1364-2001 diagrams, using
something other than JPG for importing diagrams into frame.
- Stu to write proposal for PTF 368.
- Francoise to write proposals for PTF 373, 374, and 396.
- Steve to write proposals for PTF 311, and 495.
- Sachi to write proposals for PTF 307, 312, and 313.
- All to review Generates proposal from ETF committee.
Chas did this.
- Francoise, et all to review BTF generates proposal
for the upcoming vote, with particular emphasis on
how we will address generates in VPI.
Done.
- Stu to enter new PTF item for save/restart/reset issue.
- JimG to write proposals for PTF 517, 533, and 534.
- Chas to write proposal for PTF 296.
- Francoise to lookup wording for PTF 524 in VHPI.
- Francoise will open a new PTF issue to look for situations like 25.6.15,
where multiple methods are used access the same object enclosure
- Chas to reword proposal for PTF 525.
- Draft a straw man proposal using a clean slate with no concern for
existing PLI/VPI on the best way to represent all Verilog and
SystemVerilog kinds and types. This straw man will then be used as a
basis for discussing backward compatibility with the existing reg, net,
variables, functions, and parameter diagrams. It may be decided that
full backward compatibility is not possible, or is not the best approach
moving forward.
- Sachi will file a PTF item for the clarification of what can be done
at ROsync time and putting values in future times.
- Francoise to file a PTF item that asks to specify the order that iteration
occur in, when the order is important.
- Steve to add ETF item for Annex C to remove the Informative label, but
still allow the contents to be optional.
Meeting ended at 1:55pm (EST)
7. Action items
SV-CC action items:
- Francoise to ask Peter Ashenden what was done to improve
printing from Rational Rose.
- Francoise to inquire about the feasibility of third parties
shipping the UML for the diagrams.
- Bassam to update 265 as amended.
- Michael to update 158 as amended.
- Sachi to drive finding a better solution for 052.
- Chas to add colors to proposals for 310 and 040.
- Chas to add Stu to SV-CC email alias.
PTF action items:
- Steve to compare BNF with the access available
for attributes to see if they match
- Francoise to remove "+" from tags in UML diagrams and
add vpi prefix where appropriate.
- Francoise to send out HTML for 1364-2001 diagrams, using
something other than JPG for importing diagrams into frame.
- Stu to write proposal for PTF 368.
- Francoise to write proposals for PTF 373, 374, and 396.
- Steve to write proposals for PTF 311, and 495.
- Sachi to write proposals for PTF 307, 312, and 313.
- Stu to enter new PTF item for save/restart/reset issue.
- JimG to write proposals for PTF 517, 533, and 534.
- Chas to write proposal for PTF 296.
- Francoise to lookup wording for PTF 524 in VHPI.
- Francoise will open a new PTF issue to look for situations like 25.6.15,
where multiple methods are used access the same object enclosure
- Chas to reword proposal for PTF 525.
- Draft a straw man proposal using a clean slate with no concern for
existing PLI/VPI on the best way to represent all Verilog and
SystemVerilog kinds and types. This straw man will then be used as a
basis for discussing backward compatibility with the existing reg, net,
variables, functions, and parameter diagrams. It may be decided that
full backward compatibility is not possible, or is not the best approach
moving forward.
- Sachi will file a PTF item for the clarification of what can be done
at ROsync time and putting values in future times.
- Francoise to file a PTF item that asks to specify the order that iteration
occur in, when the order is important.
- Steve to add ETF item for Annex C to remove the Informative label, but
still allow the contents to be option
8. Items for consideration at the next meeting (they already have proposals):
- NONE!
-- Charles Dawson Senior Engineering Manager NC-Verilog Team Cadence Design Systems, Inc. 270 Billerica Road Chelmsford, MA 01824 (978) 262 - 6273 chas@cadence.comReceived on Wed Dec 1 13:03:48 2004
This archive was generated by hypermail 2.1.8 : Wed Dec 01 2004 - 13:03:51 PST