Re: gEDA-user: Icarus misses unconnected nets?

[Tom Hawkins <tom@xxxxxxxxxxxxx>]

Stephen Williams wrote:
> Tom Hawkins wrote:
> | Icarus is not reporting unconnected nets with -Wall.  Am I missing
> | something?  I always thought it did.
> |
> |       1 module test (x);
> |       2   output x;
> |       3   wire b;
> |       4   assign x = b;
> |       5 endmodule
> |
> | $ iverilog -Wall test.v
> | $ # Nothing!
> |
> | I'm running 0.8.
>
> It reports unconnected *inputs* because they affect the behavior
> of the module. It is common and reasonable (I believe) to have
> unconnected outputs. Also, it reports on unconnected ports at the
> instantiation, so ports to a root module are not reported.

That makes sense.

I'm trying to debug a large, flat, ugly module -- not mine, of course. 
It has many wires feeding a lot of logic, but nothing is driving them! 
It'd be nice if Icarus reported these dangling nets, but I realize 
linting is not it's primary job.

BTW, How's vectorized iverilog coming?

-Tom

> --
> Steve Williams                "The woods are lovely, dark and deep.
> steve at icarus.com           But I have promises to keep,
> http://www.icarus.com         and lines to code before I sleep,
> http://www.picturel.com       And lines to code before I sleep."