Subject: Re: [sv-cc] [Fwd: Re: Version 2 of DPI LRM]
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Wed Mar 12 2003 - 17:30:58 PST
[John, thanks for picking this up. Here are my $0.02]
Andrzej Litwiniuk wrote:
> > To re-iterate the request John and I made in the meeting, I think
> > it is important that we more precisely define the bounds of source
> > compatability in the LRM.
>
> I believe there is enough precision there.
> The bottom line is very simple (and presented in LRM):
>
> - if an application can be compiled without any vendor-provided include
> files, it is binary compatible
>
> - if an application can be compiled without vendor-provided include files
> other than sv_src.h, then it is source compatible
>
> - if an application requires vendor-provided include files other than sv_src.h
> to be successfully compiled, then it is not source compatible
>
> Shall we enumerate the situations that require a complete knowledge of a data
> type rather than the knowledge that a type is an obscure pointer?
Just for clarification, since, by reading the minutes of today's conf call, I have the feeling that I am a little bit misunderstood
by my request for object/source compatibility:
a) the above distinction is great, but over-simplifying. If I am using a vendor-specific include file, I will not be source
compatible, by definitionem.
b) my question was that, due to the unpacked,packed data layout dilemma would it be possible that this might break the above
definitions, IFF a user defines a special data layout that can not be handled by source code recompilation?
- my understanding is now no, Andrzej waived this when adhering to his stated restrictions. If this is case, I'll go with it.
c) If there are any other restrictions a user should know to assert _her/his_ definitions do not break source compatibility, then we
definitely should enumerate them in the LRM.
Be warned. Let's assume the most possible dumb user (german abbreviation for this is 'DAU'), you have one of this type in your
committee.
-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 Mar 12 2003 - 17:31:46 PST