From: Adam Krolnik (adamk@cyrix.com)
Date: Tue Jan 26 1999 - 12:10:39 PST
Stefen writes:
I'll start the list with two basic needs:
1) Simple library usage.
User provides only part of a design and a
collection of files containing modules that may
be needed in the simulation. This works ok
with -y,-v,+libext.
2) Module name collisions.
User needs two versions of the same module. We
need a better solution than the `uselib hack.
I'll add
<p> 3) Top level modules.
User specifies names of top modules.
Compiler searches for them in libraries.
[Currently on filename specification is possible.]
4) Define libraries.
The connotations of -y, -v contain too many problems.
How about named libraries?
5) Configure design blocks.
Want ability to specify module(s) defining a block.
Want ability to specify library order for searching.
Want ability to do this separately for different blocks.
I like (these ideas - not necessarily syntax):
config ... endconfig
design <top module>
liblist <library1, library2, etc.>
path <hierarchical path> bind <library>
path <hierarchical path> liblist <library1, library2>
cell <module name> liblist <library1, library2>
library ... ;
It is interesting to note that views allowed one to define a configuration
with the same name as a module and have that be selected in preference
to the actual module. This allows one to configure extra information into
that specific block. Do we want something like this, or do we want to
make it explicit that configs take precedence over modules or do we want
them in a separate name space/separate working place.
--------------------
<p> Adam Krolnik
Verification Engineer
Cyrix - NSC.
Richardson TX. 75085
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:53:25 PDT
and
sponsored by Boyd Technology, Inc.