RE: [sv-bc] Question on compilation units & compiler directives

As a user, I disagree.

This is breaking more than 15 years of legacy use-models.

When you give a sequence of files to a tool, users expect that the
compiler directives hold from file to file. If you want to compile or
synthesize them separately, then you compile or synthesize them
separately.

Shalom


> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On
> Behalf Of Karen Pieper
> Sent: Tuesday, January 24, 2006 7:08 PM
> To: Warmke, Doug; Brad Pierce; sv-bc@eda.org
> Cc: LaFlamme, Jamie; Mehdi Mohtashemi
> Subject: RE: [sv-bc] FW: [sv-ec] Question on compilation units
> & compiler directives
> 
> I disagree that the paragraph was overlooked.  If one would
> like to use
> multiple files as a compilation unit, a compliant tool must
> support that
> via option A, and this case is covered.
> 
> Our intent was to move to a model where there was more support
> for
> separate compilation not requiring the concatenation of all of
> the
> defines across all compilation units.  This semantics is closer
> to the
> one required for a synthesis tool to support separate synthesis
> of each
> module, and for a simulation tool to be able to support
> separate
> compilation.  A user can achieve the inclusion of the defines
> by doing a
> #include and having it appear in each file.
> 
> Karen