Subject: Re: [sv-cc] Looking for proposals on DirectC/other names
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Wed Feb 19 2003 - 01:52:00 PST
Just my two cents on this:
a) I think we have to clearly distinguish our deliverables:
We basically are providing
- one new API, which is based on the Synopsys DirectC donation
- two extensions to VPI, which are providing a C API for coverage and assertion information
b) We have already choosen and voted for using the prefix sv_ for new additions, some vpi extensions are also using the vpi prefix.
This prefix is used for all of the above ...
My proposal would be to
1) name the sum of our deliverables the SystemVerilog C extensions (abbreviated by SVC extensions)
2) don't have specific names for the coverage and assertion extensions on VPI; instead refer to them as
- SVC coverage extension [to VPI]
- SVC assertion extension [to VPI]
3) have a standalone name for the new API, which is based on the Synopsys DirectC donation. I am rather neutral on this, but I
concur with Vassilios that we should not use the name of a certain product. As a result I am having therefore several proposals, in
order of my personal preference (highest favorite first):
- DCI (Direct C Interface): this recognizes the origin, without using exactly the name from Synopsys.
[Please note the blank between the 'Direct' and the 'C']. It also rather good describes how it works.
- DFI (Direct Function Interface): this might be a misnomer, because it does not reflect the task/function dualism.
But it very much gets to the point how it is working.
- FLI (Foreign Language Interface): although this might collide with VHDL
- DPI (Direct Programming Interface): I also like this proposal from Doug
- SPI (Simple Programming Interface): I hope this says what it is
The only problem I currently foresee is that we very likely should adjust the svc_bin.h and svc.h include file names to the name
choose for the DirectC API.
Yes, I know, this is much too much for just having $0.02 cents.
Regards,
-Michael
Swapnajit Mittra wrote:
> Team,
>
> As discussed in today's meeting, I am collecting
> proposals for names for what we have called as
> DirectC so far.
>
> Interestingly, I got the following mail from
> Vassilios shortly after the meeting:
>
> > As part of this we must start using an
> >Agreed upon Accellera names and not names of
> >existing products (e.g. Direct-C). We have termed
> >SVC as a description for the full standard (C
> >interface, API assertion, And API coverage). If
> >SVC is not a good descriptive, then please provide an
> >alternative. You can mention that donations and
> >where these comes from.
>
> Please send your suggestions by tomorrow and
> then, if need arises, we will arrange a poll and
> pick up a good name (only to change it later
> before DAC, as Joe commented :-)
>
> Regards,
> - Swapnajit.
>
> --
> Swapnajit Mittra
> Project VeriPage ::: http://www.angelfire.com/ca/verilog
>
> ________________________________________________________________
> Sign Up for Juno Platinum Internet Access Today
> Only $9.95 per month!
> Visit www.juno.com
--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 Feb 19 2003 - 01:52:37 PST