From: Adam Krolnik (email@example.com)
Date: Fri May 10 2002 - 09:59:53 PDT
>4. Sec 13.2.1 says that all library source text files shall be read >first by the parser.
> So if I have:
> > myparser a.v b.v c.v d.v e.v
> and b.v and e.v contain library source text, should myparser read >b.v and e.v first
13.2.1 is saying that each tool must define a filename and or command
line options for specifying the library mapping files to read.
It is not saying that you need to search through any files (verilog
or other) to figure out what looks like a library mapping file.
For example, my tool will read (by default) the file 'lib.map'.
If one does not like this name, or needs to use a different file
(for testing, etc.) my tool allows one to specify -lib <file>
and it will read this alternate file for determining the libraries.
My tool will also accept an option -nomap to disable ieee1364-2001
library mapping. One will then need to specify the verilog source(s)
using the old options.
>5. If the parse has to read the library source text first (13.2.1),
> there is not much the parser
> can do when configurations are read as the verilog modules have not >yet been parsed.
Since 13.2.1 says, 'the library source text files must be read first',
I see no way that one could reasonably mix library specifications with
verilog source code and not violate 13.2.1. I do not accept a specific
file order as that is easily missed when others use the files.
Also, note that configurations are not part of the library mapping
I think that one could write a clarification about what Dennis asked,
The syntax for library maps (A.1.1) is a separate companion language.
The syntax for configurations (A.1.2) is considered an addition to
the verilog source language.
This is conceptually what we were talking about - a separate set of
files to replace the verilog 1995 -f, -F, -v files and -y directories
that constitute a library. Configurations
take over from there, replacing the required files list from the -f,-F
options by specifying module names and the order to look at libraries.
In addition, standardizing the concepts from `uselib and making them
A. Parse library mapping files (default or specified.)
B. Elaborate libraries (what modules are in what libraries.)
C. Process verilog files/configurations specified or by options.
LSI Logic Corp.
Plano TX. 75074
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:55:37 PDT
sponsored by Boyd Technology, Inc.