RE: [sv-cc] No SV-CC meeting today

I'm thinking that you could add a revised proposal
without deleting the existing one, with a Note saying
that this new one has not yet been approved by the SV-CC.
Then the SV-CC could consider it and (assuming that
we agree to the changes) petition the Working Group
to allow a substitution on the grounds that we found
typographical inconsistencies.

Regards,
Jim Vellenga

--------------------------------------------------------- 
James H. Vellenga                            978-262-6381 
Software Architect                     (FAX) 978-262-6636 
Cadence Design Systems, Inc.         vellenga@cadence.com 
270 Billerica Rd
Chelmsford, MA 01824-4179
"We all work with partial information." 
----------------------------------------------------------  

]-----Original Message-----
]From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On 
]Behalf Of Moorhouse, Abigail
]Sent: Wednesday, June 18, 2008 1:45 PM
]To: Moorhouse, Abigail; Charlie Dawson; SV-CC
]Subject: RE: [sv-cc] No SV-CC meeting today
]
]minor change - vpiObjId is a property and should therefore come after
]the vpiAllocScheme line:
]
]#define vpiAllocScheme           656 /* Mantis 2226 */ 
]#define vpiObjId          <editor to fill>
]
]-----Original Message-----
]From: owner-sv-cc@server.eda.org [mailto:owner-sv-cc@server.eda.org] On
]Behalf Of Moorhouse, Abigail
]Sent: Wednesday, June 18, 2008 10:01 AM
]To: Charlie Dawson; SV-CC
]Subject: RE: [sv-cc] No SV-CC meeting today
]
]hi Charlie, all,
]I was hoping for a meeting because I have a couple of issues. Here is
]the first one.
]
]I have identified a couple of necessary but minor changes to 2226
](dynamic objects).
]#1 - vpiObjId doesn't have a #define
]#2 - placing the new 64-bit vpi_user.h type definitions within the
]PLI_TYPES include guards has the unfortunate consequence that 
]they don't
]get defined if there is a preceding acc_user.h or veriuser.h file
]included in the 'C' file (since it uses the same guard, but doesn't
]define the 64-bit types).
]
]I would like to either
]
]a) edit the existing proposal (preferred, but probably too late)
]b) create a new proposal to fix these things
]
]The first change is obviously necessary in order to use the Object ID!
]If I can't edit the existing proposal to add an editor-define constant
]then I will propose an actual constant so we can all agree on 
]it outside
]the 2009 spec. The second change is an actual-usage irritant 
]that people
]using the new vpi_user.h may encounter as I did.
]
]The changes are basically:
]in Draft 6/Annex L (vpi_user.h) change
]
]#ifndef PLI_TYPES
]#define PLI_TYPES
]typedef int PLI_INT32;
]typedef unsigned int PLI_UINT32;
]typedef short PLI_INT16;
]typedef unsigned short PLI_UINT16;
]typedef char PLI_BYTE8;
]typedef unsigned char PLI_UBYTE8;
]#endif
]
]to
]
]#ifndef SVPI_TYPES
]#define SVPI_TYPES
]typedef int64_t	 		PLI_INT64;
]typedef uint64_t	 	      PLI_UINT64;
]#endif#ifndef PLI_TYPES
]#define PLI_TYPES
]typedef int PLI_INT32;
]typedef unsigned int PLI_UINT32;
]typedef short PLI_INT16;
]typedef unsigned short PLI_UINT16;
]typedef char PLI_BYTE8;
]typedef unsigned char PLI_UBYTE8;
]#endif
]
]
](the 2226 proposal has the new types within the original include guard)
]and in Draft 6/Annex O (sv_vpi_user.h) change #define vpiPackedArrayNet
]693 to 
]
]#define vpiPackedArrayNet 693
]#define vpiObjId          <editor to fill>
]
]Abi
]-----Original Message-----
]From: owner-sv-cc@server.eda.org [mailto:owner-sv-cc@server.eda.org] On
]Behalf Of Charlie Dawson
]Sent: Wednesday, June 18, 2008 5:53 AM
]To: SV-CC
]Subject: [sv-cc] No SV-CC meeting today
]
]Hi All,
]
]Sorry for the short notice.  Cadence has a meeting today which 
]conflicts
]with the SV-CC meeting.  Without any Cadence folks there, I am not sure
]we would get quorum, so I am going to cancel it.  Please let me know if
]there was something important that we needed to discuss.
]
]   -Chas
]
]
]--
]Charles Dawson
]Senior Engineering Manager
]NC-Verilog Team
]Cadence Design Systems, Inc.
]270 Billerica Road
]Chelmsford, MA  01824
](978) 262 - 6273
]chas@cadence.com
]
]
]--
]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.
]
]
]

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