From: Steven Sharp (sharp@cadence.com)
Date: Tue Jun 18 2002 - 16:08:10 PDT
Precedence: bulk
I don't know much about the config stuff, but here is my best guess after
talking to someone who knows it much better.
The comments seem to be based on the idea of using the library declarations
to find the source code for modules, so they can be compiled in, like the
Verilog-XL -y and -v options. Verilog-XL has to find and then parse the
source code because it has no concept of a compiled library.
The config stuff seems to be based around the concept of compiled libraries.
The library paths tell the parser which library to put the compiled form of
a given source file in, based on where the source file came from. But it
still assumes that the user specifies which source files to compile. And
then the configs determine which library to get the definition of a module
from. It is not clear to me that the parser would ever use the file paths
to search for additional source files that were not explicitly specified
by the user (though section 13.4.2 might be describing such a thing). If
tools don't do this, then the issues being raised don't occur.
Am I missing something?
Steven Sharp
sharp@cadence.com
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:55:37 PDT
and
sponsored by Boyd Technology, Inc.