7

I have a question on `default_nettype directive of SystemVerilog.

By default, the following code is ok.

module m1 (
   input  logic i1,
   output logic o1
   );

   logic  l1;
   assign l1 = i1;
   assign o1 = l1;
endmodule

However, when I change the default net type to none:

`default_nettype none

only i1 causes an error:

ERROR: [VRFC 10-1103] net type must be explicitly specified for i1 when default_nettype is none ...

Why does only input logic i1 cause an error and require explicit wire, but output logic o1 and logic l1 does not?

Improve this question
2
  • Which compiler does it? in your case there is no reason for any compiler to complain about the net type. And actually, i did not find one which does. Commented Oct 22, 2019 at 14:59
  • 1
    I am using Vivado 2019.1, and the error message above is produced when I run simulation. ModelSim lite included in Intel's Quartus Prime also produces a similar error message. Thanks. Commented Oct 23, 2019 at 3:20

2 Answers 2

Reset to default
8

Verilog has too many implicit rules to accommodate lazy programmers (i.e. people who were interested in designing hardware, not writing software)

This error is explained in section 23.2.2.3 Rules for determining port kind, data type, and direction

For the first port in an ANSI style port list:

  • If the port kind is omitted:
    • For input and inout ports, the port shall default to a net of default net type. The default net type can be changed using the `default_nettype compiler directive

This implicit 'net' port rule is the opposite of what is used when declaring output ports, and all other declarations outside of ports. The reason behind this is that input ports are an overwhelmingly majority of ports used in a module, and keeping ports connections as wires allows for port collapsing, which is more efficient for simulation.

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Having inputs listed as wire can be done without implications. However outputs can be driven with assign (wire) or always process (reg). Is wire beneficial here as well for simulation effectiveness?
@Moberg, this needs to be asked as a new question with example code. The original question was only about declaring ports, not how they are driven.
2

This is the confusing part of SystemVerilog. Your code works on my simulator, that outputs a warning instead of an error.

If you dive enough in help messages you get that the "type" of the identifier (as in net versus var, opposing to "datatype" which is logic or whatever else) is context sensitive, and specifically input ports are by default nets, while output ports are by default variables. This means that with "default_nettype none" all your input ports are effectively not fully described, because the compiler does not know the resolution function for the net (you might want a wand, for example). Your output ports, being variables, need no resolution function and so no error is thrown there.

Since you cannot really connect the same port to more than one signal unless you really try to this seems redundant to me, but it might be needed due to net coercion rules for elaboration if the input net is driven by more than one assign elsewhere in the design.

My understanding is that "default_nettype none" is mostly used to ensure you do not have undeclared identifiers (leading to width mismatch due to single bit inference) and a port is declared, so you might check if your tool has the option of inferring a wire for ports anyway (again, my simulator outputs a warning and does this by default, and the synthesizer does not complain either).

Other than that, the only workaround I see is going for "default_nettype none" first thing after the ANSI port declaration and "default_nettype wire" last thing before endmodule, in every module. We cannot do that, as per 1800-2017 22.8:

The directive `default_nettype controls the net type created for implicit net declarations (see 6.10). It can be used only outside design elements.

The reference for implicit net declaration is section 6.10 in IEEE 1800-2017, although following the mentioned sections from there seems to point to non-ANSI declarations only... you might need a deeper dive to fully understand the matter.

Improve this answer

2 Comments

Thanks for useful suggestions. For portable codes, I would like to avoid setting tool options. But putting `default_nettype none/wire in modules is a new idea to me.
I found out why it is a new idea... it's because it is prohibited (which sucks, honestly, but I believe there are good reasons behind it!) Editing the answer to make it clear to possible readers

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.