[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnucap-devel] Netnames in Gnucap
From: |
Dan McMahill |
Subject: |
Re: [Gnucap-devel] Netnames in Gnucap |
Date: |
Sat, 15 Jan 2005 09:06:46 -0500 |
User-agent: |
Mutt/1.4.2.1i |
On Sat, Oct 30, 2004 at 10:25:57AM -0400, Al Davis wrote:
> On Saturday 30 October 2004 09:40 am, Stuart Brorson wrote:
> > One of the problems I've had with Gnucap in the past is that
> > almost all my netlists cause it to barf. A major reason is
> > that I have lots of named nets in my designs, whereas it
> > looks to me like Gnucap only tolerates numbered nets (a la
> > old-time SPICE).
>
> If you do ".option namednodes" it will take named nodes.
[snip]
> The reason it is undocumented and off by default is that some
> things don't work in nasty ways, and I will probably remove the
> option and make it named nodes always. The option is there as
> a development aid, so the old still works while the new is
> being developed.
[snip]
> really does need to remain int internally. The current scheme
> is not as efficient as it should be. The way to handle it is
> to map name to number on readin, and number to name on
> printout. The functions are there. It is just a matter of
> using it where it needs to be used. It's actually almost done.
[snip]
Any progress on this? I was going to try out gnucap for something
the other day where I had a netlist from a different tool (spectre)
and every single node is named, not numbered.
-Dan
--
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Gnucap-devel] Netnames in Gnucap,
Dan McMahill <=