Team,
By now, you have probably seen the email that
David has sent on bug database. As we move to
this new system, it will be much easier for us
to maintain the bug lifecycles, even though we
may encounter some teething problem initially.
Here are some suggestins from my side. Please
feel free to debate them or add yours to the
list.
o Joao will publish a last rev of the buglist
in Excel format. Joao, please do this ASAP as
we are little behind in maintaining that list.
o We will switch over to the bug system after that
and I will initially assign all the bugs to Joao
during the period of transition. (One is already
assigned to him as a test).
o I will ask David to give logins to Francoise,
Doug, Michael and Bassam as representatives of
various companies. Ghassan, Joao and I already
have logins.
o We will dynamically assign/re-assign the
ownership of a bug after that depending on
how things move.
o So far, I believe, we have three classes
of bugs (1) Agreed upon: mainly typos and text
changes. (2) Under discussion and (3) Noted
but not yet discussed. Initially I will keep
ALL of them open but I expect to move type (1)
to move quickly to a CLOSED status in one
meeting or so.
Given these and the timing of other things,
we will have a special meeting on next Wednesday
(07/14). Note that we will NOT have a meeting
tomorrow.
-- Swapnajit Mittra Project VeriPage ::: http://www.project-veripage.com/ Please note: message attached
attached mail follows:
Sorry, I have been a bit delayed with updating the spreadsheet (Synopsys is
in a shutdown,
I've had some vacation to enjoy, etc). Anyway, I should have the errata
updated soon.
Joao
============================================================================
==
Joao Geada, PhD Principal Engineer Verif Tech
Group
Synopsys, Inc TEL: (508)
263-8083
377 Simarano Drive, Suite 300, FAX: (508)
263-8069
Marlboro, MA 01752, USA
============================================================================
==
In other words - and this is the rock solid principle on which the whole of
the
Corporation's Galaxy-wide success is founded - their fundamental design
flaws
are completely hidden by their superficial design flaws.
- Douglas Adams, Hitchhiker's Guide to the Galaxy
-----Original Message-----
From: Duncan, Ralph [mailto:ralph_duncan@mentorg.com]
Sent: Tuesday, July 06, 2004 4:02 PM
To: Francoise Martinolle
Cc: Swapnajit Mittra; Joao.Geada@synopsys.COM
Subject: Current SV-CC Errata?
Francoise,
I don't know what the most current errata source is. Possible sources
are:
. Joao's XL errata file, but the last one I've seen may date from a 5/25
email.
. The 'new bug system' at www.eda.org/svdb touted in a Dave Smith email of
6/2.
(I just checked it as a 'guest' user and it reported only 1 SV-CC open
errata).
Swapnajit, Joao, do you have any advice?
Thanks, regardless,
Ralph
Ralph Duncan
Mentor Graphics, Inc.
San Jose, CA
----------------------------------------------------------------------------
-- From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Francoise Martinolle Sent: Tuesday, July 06, 2004 11:46 AM To: Duncan, Ralph; sv-cc@eda.org Subject: Re: [sv-cc] Errata for SV3.1A (Imported Task Return Type) How do I access the current errata list? Francoise ' At 04:51 PM 6/17/2004 -0400, Duncan, Ralph wrote: 1. Obsolete Definition of Import Task Return Type (27.4.4) The text states that a DPI import task has a return type of void but the required return type is int (LRM 3.1a sections 27.7, 27.8). where: Section 27.4.4, paragraph 2, final sentence. Before: "Imported tasks never return a result, and thus are always declared in foreign code as void functions." After: "Imported tasks always return an int result as part of the DPI disable protocol and, thus, are declared in foreign code as int functions (see Sections 27.7 and 27.8)." ________________________________________________________________ The best thing to hit the Internet in years - Juno SpeedBand! Surf the Web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!Received on Tue Jul 6 19:14:59 2004
This archive was generated by hypermail 2.1.8 : Tue Jul 06 2004 - 19:15:01 PDT