This number does not work outside the U.S. !!!
-Michael
Francoise Martinolle wrote:
> It is 1 888 635-9997
>
>
> At 04:20 PM 8/10/2004 -0400, Joao Geada wrote:
>
>
>> Hi all,
>>
>> we'll have an sv-cc meeting tomorrow.
>> Time: 9:00am PST, 12:00pm EST
>> Conference number: 1-800-635 9997
>> Participant code: 2638073
>>
>>
>> Agenda:
>> - summary of last week's errata meeting
>> - overview of errata process and significance of the various status codes
>> - go over the 38 bugs currently in the sv-cc category and start resolving
>> items and/or assigning them to people to create resolution proposals
>>
>> For reference, attached below is the list of all current sv-cc errata (39 errata items altogether)
>>
>>
>> Viewing Bugs (1 - 39 / 39) [ Print Reports ] [ CSV Export ]
>> PID # Category Severity Status Updated Summary
>>
>> 0000158 SV-CC minor new 08-09-04 Restructure sv_vpi_user.h to partition the VPI in a more logical form
>> 0000125 SV-CC feature new 08-06-04 "typespec", not "type spec" in VPI variables object model
>> 0000124 SV-CC text new 08-06-04 Inconsistent VPI names: var(iable) drivers and loads
>> 0000123 SV-CC minor new 08-06-04 Clarify meaning of "member typespec" in VPI
>> 0000122 SV-CC minor new 08-06-04 Eliminate property vpiTypedefType as redundant
>> 0000121 SV-CC text new 08-06-04 Erroneously numbered Note "5" in VPI Typespec object model
>> 0000080 SV-CC minor new 08-06-04 vpiTypedef property issues
>> 0000079 SV-CC minor new 08-06-04 Clarify TRUE/true and FALSE/false values for VPI object model
>> 0000078 SV-CC minor new 08-06-04 Handle type 'reg' as interchangeable with type 'logic'
>> 0000077 SV-CC text new 08-06-04 VPI diagram for instances shouldn't refer to reg objects
>> 0000072 SV-CC minor assigned (joao) 08-06-04 LRM specifies number references for vpi defines, only to be done in annex
>> 0000070 SV-CC text assigned (joao) 08-06-04 Replace vpiAssertionDirective reference in the index by vpiAssertionType
>> 0000069 1 SV-CC text assigned (joao) 08-06-04 vpi_get() use vpiAssertionType instead of vpiAssertionDirective
>> 0000068 SV-CC minor assigned (joao) 08-06-04 VPI access to assertion local variables
>> 0000067 SV-CC text assigned (joao) 08-06-04 Add vpiAssertionType to enumnerations
>> 0000066 SV-CC text assigned (joao) 08-06-04 Error in VPI assertion traversal examples
>> 0000065 SV-CC minor assigned (joao) 08-06-04 Note 19 in section 31.10 is wrong
>> 0000064 SV-CC minor assigned (joao) 08-06-04 Note 20 of section 31.10 is unclear
>> 0000063 SV-CC major assigned (joao) 08-06-04 Conflicts in notes 2. 4. and 11 of section 31.10
>> 0000062 SV-CC major assigned (joao) 08-06-04 Conflicting vpiArray property descriptions in 31.10
>> 0000061 SV-CC major assigned (joao) 08-06-04 Meaning of vpiMultiArray depends on 1364 but is in conflict with it
>> 0000060 SV-CC text assigned (joao) 08-06-04 bad cross-reference in notes 3 and 4 of diagram 31.10
>> 0000059 SV-CC text assigned (joao) 08-06-04 Typo in note 3 of diagrams 31.12
>> 0000058 SV-CC trivial assigned (joao) 08-06-04 type of vpiTagged property in 31.12 is wrong
>> 0000057 SV-CC feature assigned (joao) 08-06-04 VPI cannot access the dependent packages for a given instance
>> 0000056 SV-CC minor assigned (joao) 08-06-04 vpi_handle_by_name on imported items?
>> 0000055 SV-CC major assigned (joao) 08-06-04 fullnames of declarations in the global scope of a compilation unit
>> 0000054 SV-CC major assigned (joao) 08-06-04 What is the vpiFullName of a package?
>> 0000053 SV-CC major assigned (joao) 08-06-04 VPI access to instances and packages is incorrect
>> 0000052 SV-CC minor assigned (joao) 08-06-04 vpiFuncType return values for systemVerilog datatypes
>> 0000050 1 SV-CC major confirmed 08-06-04 Change DPI svLogicVec32 representation to match PLI/VPI aval/bval representation
>> 0000049 1 SV-CC minor assigned (joao) 08-06-04 Necessity of specifying import fn return type
>> 0000048 1 SV-CC minor assigned (joao) 08-06-04 Imported task return type: obsolete definition
>> 0000047 1 SV-CC text assigned (joao) 08-06-04 Erroneous cross-references [E.7.1, E.7.3, E.7.8]
>> 0000046 1 SV-CC text assigned (joao) 08-06-04 Grammar and typographical errors (E.6.3, E.9.4)
>> 0000045 SV-CC feature assigned (joao) 08-06-04 VPI access to elements of complex literals
>> 0000044 SV-CC feature assigned (joao) 08-06-04 var bit vs. vpiVarBitVar in VPI
>> 0000040 SV-CC major assigned (joao) 08-06-04 diagram for parameter is missing
>> 0000005 1 SV-CC text resolved (joao) 08-06-04 Compatibility of Section E.6.7 of SV3.1A with IEEE PLI aval and bval
>>
>> ==============================================================================
>> Joao Geada, PhD Principal Engineer Verification Group
>> Synopsys, Inc TEL: (508) 263-8083
>> 377 Simarano Drive, Suite 300, FAX: (508) 263-8069
>> Marlboro, MA 01752, USA
>> ==============================================================================
>
-- NOTE: The content of this message may contain personal views which are not neccessarily the views of Freescale, unless specifically stated. ___________________________________________________ | | _ | Michael Rohleder Tel: +49-89-92103-259 | _ / )| Freescale Semiconductor Fax: +49-89-92103-680 |( \ / / | Freescale Halbleiter Deutschland GmbH | \ \ _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_ (((\ \>|_/ > < \_|</ /))) (\\\\ \_/ / mailto:Michael.Rohleder@freescale.com \ \_/ ////) \ /_______________________________________________\ / \ _/ \_ / / / \ \ The information contained in this email has been classified as: General Business Information ( ) Freescale Internal Use Only ( ) Freescale Confidential Proprietary ( ) *** This note may contain Freescale Confidential Proprietary or Freescale Internal Use Only Information and is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you! ***Received on Wed Aug 11 09:07:12 2004
This archive was generated by hypermail 2.1.8 : Wed Aug 11 2004 - 09:07:13 PDT