Subject: Re: [sv-cc] Updated proposal for C/C++ file inclusion
From: Francoise Martinolle (fm@cadence.com)
Date: Mon Jan 27 2003 - 15:31:27 PST
Michael,
I don't understand the multiple occurrences rule. You say that a library
must and
will only be loaded once.
For example if my entry in my bootstrap file says:
#!SV_LIBRARIES
myclibs/lib1
and I have a switch -sv_lib clibs/lib1
These could be the same library copied in 2 different places.
Does it mean I only load the first occurrence of lib1: myclibs/lib1?
My general comment is that you propose not only 1 solution to specify the
object or source
code but 3 solutions which can be intermixed. Why does the user need 3 of them?
it adds flexibility but complexity. Why not just enforce 1 of them. That
makes it
easier for the vendor and for the user. In fact you want 1 standard way.
I would prefer the bootstrap file approach because this is the way that a
3rd party can
deliver and package directC code for another user. The 3rd party will
provide the bootstrap
file as part of the directC delivered code. If other methods would be
chosen, the only way to
specify them would be to provide it in the documentation. Instead the
directC code
delivered provide a self contained file for using it.
Francoise
'
At 10:24 PM 1/27/2003 +0100, Michael Rohleder wrote:
>Hi all,
>
>please find below the updated proposal for the inclusion of C/C++ code. As
>requested in the last meeting, I have split it into two
>parts: Object Code inclusion and Source Code inclusion. The result
>consists now of three parts:
> . a common introduction
> . the part about Object Code inclusion
> . the part about Source Code inclusion
>[the rationale behind this organization is that the addition of a PLI/VPI
>inclusion mechanism as requested in the meeting could be
>easily accomplished as third part, with only minor changes to the
>introduction]
>I have further added a complete set of switch settings for all environment
>variables (as requested by Joao) and further provided a
>mechanism to disable the usage of environment variables. Change bars are
>used to show all modifications. Since I have done some
>restructuring in the switch/variable parts of the source code part, there
>are a lot of changes in this part ...
>
>Have fun reviewing!
>
>Best regards,
>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 : Mon Jan 27 2003 - 15:35:10 PST