From: Stefen Boyd (stefen@boyd.com)
Date: Wed Jan 27 1999 - 09:08:00 PST
BAD MSG:
Hi all,
To try to get our focus on what we are trying to
accomplish with the config proposal, I would like to
compile a "top ten" list of requirements that
can drive the proposal.
X-Lines: 55
Content-Type: text/plain; charset="us-ascii"
Content-Length: 1483
X-Status: $$$$
X-UID: 0000000829
Status: RO
In the next btf meeting I would like to spend time
clarifying these and prioritizing them. This will
help us sort out the required vs. frivolous elements
of our proposal.
I've thrown in a couple to start things off - and Adam K.
added a few more. Please add your expectations of what
problems configs should solve. I don't care if it's
off-the-wall - I just want to make sure we cover everything.
My two:
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.
Adam K. added:
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.
<p>Regards,
Stefen
--------------------
Stefen Boyd
__
| \ ____
|_/_ |
| \ |__
|___/oyd |
|___nterprises
stefen@boyd.com
(408)739-BOYD
(408)481-9658 (fax)
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:53:25 PDT
and
sponsored by Boyd Technology, Inc.