Subject: RE: Agenda for Our Next Meeting - July 23
From: Ghassan Khoory (Ghassan.Khoory@synopsys.com)
Date: Tue Jul 23 2002 - 05:54:11 PDT
Will do next time.
/gjk
-----Original Message-----
From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org]On Behalf Of
Michael McNamara
Sent: Monday, July 22, 2002 6:32 PM
To: Ghassan Khoory
Cc: sv-cc@eda.org
Subject: RE: Agenda for Our Next Meeting - July 23
Ghassan Khoory writes:
> [1 <text/plain; iso-8859-1 (7bit)>]
> Pls. see agenda attached.
> Thanks,
> /gjk
> [2 sv-cc-meeting agenda 072302.doc <application/msword>]
>
Please send agenda and minutes as plain ascii!!
1) It is much easier to read when one doesn't need to fire up star office
to find the conference call number.
2) the overall size of the message is much smaller (1400 bytes versus
32998)
3) it is hard to attach a virus to a simple ascii message.
Here is the decoded data:
oSV-CC
Agenda
July 23, 2002
Meetings Schedule and Call Info:
PARTICIPANT INFORMATION:
-----------------------
All Participants should use the following information to reach the
conference call:
* PARTICIPANT CODE: 707131
* Toll Free Dial In Number: (877)807-5706
* International Access/Caller Paid Dial In Number: (225)383-8961
July 23
August 6, 20
September 3, 17
October 1, 15, 29
November 12, 26
December 10, 24?
January 7, 21
Agenda:
1. Updates on issues raised in last meeting about appropriate
committee for what sv-cc is being chartered with: Any C/C++ verilog
construct calls need to be coordinated with the SV-EC committee Any
C/C++ calls for assertions need to be coordinated with the SV-AC
committee Coverage C/C++ calls are independent and belong in this
committee
2. Start with the C/C++ interface. Get an agreement on what foreign
language the interface has to support. Members discussion, from our
last meeting, was in favor of a standard C interface with everything
else to be left optional or undefined at this time.
3. Create two teams from committee members to come back with in 2
weeks with draft requirements/constraints on the following:
a.Semantics definition of value interchange across Verilog/C boundary
for primitive and complex types in SystemVerilog b.Details of C
interface to verilog functions/tasks & model and semantics definition
of C based instances
The idea is to have the teams work on those items in between meetings.
This archive was generated by hypermail 2b28 : Tue Jul 23 2002 - 05:56:01 PDT