Subject: Re: [sv-cc] Version 2 of DPI LRM] - compatibility, C Layer
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Fri Mar 14 2003 - 10:45:25 PST
What about creating a new subsection
"A.4.3 Include files and Portability"
and moving the last sentences of A.4.1 and A.4.2 into this subsection. Then this would be the right place to include the additional information about vendor specific include files.
Just a thought.
-Michael
Andrzej Litwiniuk wrote:
> > > > My understanding was this:
> > > >
> > > > Aplication requires:
> > > >
> > > > svc.h only, no svc_src.h, no vendor_specific.h
> > > > --> Guaranteed binary compatible
> > > >
> > > > svc.h, svc_src.h, no vendor_specific.h
> > > > --> Guaranteed source compatible
> > > >
> > > > svc.h, svc_src.h, vendor_specific.h
> > > > --> No compatibility guaranteed
> > >
> > > Such has been and still is my understanding, too.
> >
> > DOUG: Good - this makes sense.
> > But it was not my understanding.
>
> Doug & JohnS,
>
> Thank you for your comments.
>
> > Can you please enter a table in the LRM, as simply put
> > as John's text here?
>
> OK, such table may make the information stand out. Just please advise
> where to put it. Section "A.3 Portability" could seem the best place, but
> the include files are not introduced in this section yet.
> So, Section "A.4 Include files"?
>
> Now, let me quote excerpts from "A.4 Include files".
>
> ===== Second and third paragraph of "A.4 Include files":
>
> Binary compatibility of an application depends on the data types of the values passed through the interface. If all corresponding type definitions can be written in C without the need to include an svc_src.h file, then an application is binary compatible. If an svc_src.h file is required, then the application is not binary compatible and needs to be recompiled for each simulator of choice.
>
> Applications that pass solely C-compatible data types or standalone packed arrays (both 2-state and 4-state) require only an svc.h file and, therefore, are binary compatible with all simulators. Applications that use complex data types which are constructed of both SystemVerilog packed arrays and C-compatible types, also require an svc_src.h file and, therefore, are not binary compatible with all simulators. They are source-level compatible, however.
>
> ===== Last sentence of of "A.4.1 svc.h include file":
>
> Applications which only use svc.h shall be binary-compatible with all SystemVerilog simulators.
>
> ===== Last sentence of of "A.4.2 svc_src.h include file":
>
> Applications that require an svc_src.h file are only source-level compatible, i.e., they need to be compiled with the version of svc_src.h provided for a particular implementation of SystemVerilog.
>
> =====
>
> I agree that no vendor_specific.h has been mentioned, so it may be not obvious
> that a program that includes vendor specific include file, does depend
> on a vendor specific include file.
> Seriously, JohnS's table-like form is very clear, but I don't know where
> is the best place for it and what to do with then redundant information.
>
> Thanks and regards,
> Andrzej
--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 : Fri Mar 14 2003 - 11:21:33 PST