Subject: RE: [sv-cc] Minutes of the Conference Call - SV-CC committee 17-Dec-2003
From: David W. Smith (David.Smith@synopsys.com)
Date: Wed Dec 17 2003 - 11:10:56 PST
Greetings,
Just a note. The final deadline for getting items into Draft 3 (end of
December) is this Friday. This means that they have to be mailed to me by
Friday so I have a chance of actually working on it on Friday. Anything that
comes in after that date will not be in draft 3. This is due to the holidays
and other commitments. I hope this is not a problem.
Please let me know what I can expect so that I can plan my time over the
next couple of days.
Regards
David
-----Original Message-----
From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Michael
Rohleder
Sent: Wednesday, December 17, 2003 10:32 AM
To: CC DWG, SystemVerilog
Subject: [sv-cc] Minutes of the Conference Call - SV-CC committee
17-Dec-2003
Attendees:
Francoise
Joao
Ralph
Michael
Swapnajit
Bassam
Avinash
Acceptance of previous minutes.
Proposed by Ralph, Accepted by Michael
Swapnajit asked Joao about the status of the VPI extensions.
Joao will send a final revision (containing any feedback received until then
so far) by the end of this week.
Schedule discussion. Bassam presented our status to Vassilios, agreement
from him is still pending but
there was no pushback; this will leave us some weeks into the next year, but
there is no further time left.
Remaining issues that have to be solved
- Reader will have to close all technical issues by end of this week.
Any comments need to be provided by the end of this week.
- As VPI extensions are already late, we will only have the first week of
January for finalizing this. Joao
will do his best and provide a new version by end of this week.
- Assertion API errata
Most companies are closed over the X-mas period. Cadence, Synopsys, and
Motorola are shut down.
We'll have to send a draft version of the LRM to external experts very
likely at Jan, 2nd (2004). So we
need to finish all technology changes in the week Jan, 5th to Jan, 9th.
(second week of January).
Final acceptance vote for the reader API by the end of second week of
January; general VPI will be
shortly afterwards. This is a tight schedule! Especially since there will be
a lot of vacation inbetween.
Reader API:
Swapnajit asked Bassam for feedback about the two issues.
a) Believes that Joao's suggestion might be leading to a faster solution of
this problem, he proposes that
we just do the cleanup.
Joao mentions that we can not fix the link time issues of two
simulators, we should not go into this space.
Bassam, thinks that this might change over time, this is a useful
concept, we might just not have enough
time to define it correct now.
Michael thinks, if we can go one step in the right direction then this
will be rather useful now!
Joao has sent a proposal just before the meeting. There is just one
global function that provides the
name of the library; this is a bootstrap function. We don't have to
call it vpi_read_init(), we can call
it vpi_extend().
Bassam asked how crucial it is to have the vpiHandle data type fixed.
Joao proposed to just update the examples, not the document.
The confusion turned out to be a terminology problem, we are mostly in
agreement about the bootstrap
functionality.
Joao would do it with a defined structure, where there are the function
pointers located that are then
called.
Michael requested to have a size and version information in this
structure for later extensions, and
state in the standard that this structure may only be extended with
additional functions, the ordering
of the functions must not change.
Francoise suggests to pair the function pointer with the name of the
function. Joao and Michael don't
see the benefit.
b) Swapnajit asked Michael to be the owner of the second errata, this means
creating an assertion errata
for http://www.eda.org/sv-cc/hm/1640.html. Michael volunteered :-)
Bassam discussed the changes requested here:
1st issue.
- const and similar things. Michael and Bassam think that this is in
the hand of the IEEE committee.
Everybody agrees.
2nd issue.
- Francoise's suggestion, where Michael provided already a proposal.
Bassam believes this is useful.
Michael will cross-check and put into the new errata.
3rd issue.
- Francoise suggested to explain what the time is. Bassam thinks this
is in line with other VPI functions.
Michael suggested to create a list where it is explained which time
is related to which reason.
4th issue.
- Bassam believes this is not an errata.
Michael will do all suggested changes by this weekend and send to Bassam for
initial review, then to the team.
There will be no conference call on friday. The next two weeks will be
vacation time.
Next conference call will be on Jan 7th _and_ Jan 9th.
Merry Christmas and a Happy New Year to everybody reading this!
-Michael
--NOTE: The content of this message may contain personal views which are not neccessarily the views of Motorola, unless specifically stated.
___________________________________________________ | | _ | Michael Rohleder Tel: +49-89-92103-259 | _ / )| Software Technologist Fax: +49-89-92103-680 |( \ / / | Motorola, Semiconductor Products, System Design | \ \ _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_ (((\ \>|_/ > < \_|</ /))) (\\\\ \_/ / mailto:Michael.Rohleder@motorola.com \ \_/ ////) \ /_______________________________________________\ / \ _/ \_ / / / \ \
The information contained in this email has been classified as: Motorola General Business Information (x) Motorola Internal Use Only ( ) Motorola Confidential Proprietary ( )
*** This note may contain Motorola Confidential Proprietary or Motorola 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! ***
This archive was generated by hypermail 2b28 : Wed Dec 17 2003 - 11:13:03 PST