Subject: Re: [sv-bc] Proposal for extern modules
From: Peter Flake (Peter.Flake@synopsys.com)
Date: Wed Feb 19 2003 - 06:10:46 PST
Steven,
The problem with dummy modules is that you have to maintain two port lists,
the real one and the dummy one.
The extern module can be automatically checked against the real module or
the real one can use the extern.
Peter.
At 14:28 18/02/2003 -0500, Steven Sharp wrote:
>Karen,
>
>Like Adam, I don't understand why you can't use the actual module
>declarations.
>They are apparently available, since you mentioned using scripts to create
>external declarations from them. And you proposed a .* syntax for the module
>declaration to make it use the port list from the external declaration, again
>implying that both were available.
>
>If there is some situation where the real module declaration isn't available,
>you could always use a dummy module (AKA shell or stub). They look pretty
>much like your extern declarations; just take the word "extern" off the front
>and add the word "endmodule" to the end. And if the synthesis compiler needs
>to know that these are dummy declarations, you can put the "extern" back on
>as an attribute. Also, configs could be used to compile all of the stub
>modules into a separate library if desired.
>
>Steven Sharp
>sharp@cadence.com
This archive was generated by hypermail 2b28 : Wed Feb 19 2003 - 06:21:27 PST