Search the Community
Showing results for tags 'default'.
Found 2 results
I am working on a large project with multiple Verilog/SystemVerilog config-endconfig files. Many of the config files have the statement: default liblist gates_lib work; I understand "default liblist" and the "gates_lib." I have not previously seen the "work" library at the end of the default liblist statement. Can someone explain what this is used for? I don't think there are any libraries specifically defined for "work." This looks like it might be related to separate compilation. The IEEE 1800-2017 Standard does not show any examples with the added "work" library. I am just trying to figure out if I really need the "work" portion of this liblist statement (very large project so it is tricky to hunt down all of the dependencies). Regards - Cliff Cummings
May a module or interface have default 'no-connect' port connections, for ports that we don't need to connect? I need to use an interface which is shared between testbenches. I instantiate it a lot and don't use many of the ports (i.e. they can be 'no connects') Using Cadence irun, I get this warning when I don't connect inputs to the interface: ncelab: *W,CUVWSI With tasks/functions, I can have a default value for an input argument. Is there anything similar for interfaces (or modules for that matter)? Rather than creating a bunch of dummy inputs for these ports that are not relevant to me, I'd like to change the interface somehow to clear up the warnings for cases where I don't want to use them. trying to clean up some warnings, thanks Note: the interface inputs mentioned are being used for a small piece of internal control logic in the interface. I suppose someone might suggest using parameterized interfaces. I don't recall offhand, but believe there is a reason that we are not using a parameterized interface for this. I'll have to check with the original developer.