Subject: Re: [sv-bc] Need help on "library file_path syntax"
From: Eric Olson (eolson@cisco.com)
Date: Fri Oct 31 2003 - 12:30:25 PST
The lib.map file is a single file (plus includes) that is parsed before
any verilog files read. It is probably not a good idea to allow verilog
in the lib.map file and meaningless to inlcude lib.map code in verilog
source. (it is too late) There are no scoping rules for libmap
libraries, it is a single flat file. Allowing for lib.map data in
multiple files is a serious extension to the standard that needs to be
more carefully planned.
As for the /* comments */, I personally thing they should be allowed in
the lib.map file. (you can share the preprocessor). All
'file_path_spec's should be strings. The "<" and ">" in the include
statement was a typo in the verilog 2K standard. Traditionally (C++,
etc) <file> is a file name that can be found in the library search
path. Using a string allows all files systems to name files using
whatever characters they wish.
Steven Sharp wrote:
>I believe that SV is allowing library mapping to be specified in the Verilog
>source. And since Verilog source can have comments, that leads to this
>problem.
>
>I think that allowing library mapping in the Verilog source is going in the
>wrong direction. The IEEE VSG is considering going the other direction, and
>only allowing configs in the lib.map file, not the Verilog source.
>
>Steven Sharp
>sharp@cadence.com
>
>
>
This archive was generated by hypermail 2b28 : Fri Oct 31 2003 - 12:36:19 PST