TDEB Top Bar

Trending
Semiconductor Industry News — The Digital Electronics Blog
Follow Us

TDEB Masthead

The Semiconductor Hub

Semiconductors.  Chips and Systems.  Innovation.

Indexed by leading Search Engines, AI and referenced by Engineers worldwide 500+ Articles 10M+ Pageviews 30+ Reports 50+ Citations

Comprehensive Verilog Tutorials: Introduction and History

Aarthi Chinappa
by
0
Share Facebook X LinkedIn WhatsApp Email

The history of the Verilog HDL goes back to the 1980s, when Gateway Design Automation developed the Verilog-XL logic simulator, and with it a hardware description language. Cadence Design Systems acquired Gateway in 1989, and with it the rights to the language and the simulator. In 1990 Cadence put the language into the public domain, with the intention that it should become a standard, non-proprietary language.

From one company's language to an IEEE standard

Once Verilog was public, an industry group, Open Verilog International (OVI), took charge of it and took the language through the IEEE standardization process. In December 1995 Verilog became IEEE Std 1364-1995. A revised version followed as IEEE Std 1364-2001, which was the version most designers used when this post was first written in 2006.

OVI later merged with VHDL International to form Accellera, which continued to develop standards for the electronic design industry (Accellera, about the organization). Accellera also developed SystemVerilog, a set of extensions to Verilog for design and verification, and donated it to the IEEE.

Correction: what happened after 2001

The original version of this post said that IEEE 1364-2001 "is the current version" and that Verilog is maintained by Accellera. Neither holds today, and the first was already changing in 2006:

  • A further revision, IEEE 1364-2005, was the last stand-alone Verilog standard. IEEE now lists it as superseded.
  • SystemVerilog became its own IEEE standard, IEEE 1800-2005, defined as extensions to the 2005 Verilog standard.
  • In 2009 the IEEE merged the two into a single standard, IEEE 1800-2009, so that users have one document covering base Verilog and the SystemVerilog extensions.
  • The active standard today is IEEE 1800-2023, SystemVerilog, described by the IEEE as a unified hardware design, specification and verification language. Plain Verilog lives on as a subset of it.

So the answer to "who maintains Verilog?" is now: the IEEE, as part of the SystemVerilog standard.

Why the history matters to a working engineer

  • Tool switches: simulators and synthesis tools often ask which language version to compile against. Old code written to 1364-1995 can behave differently, or fail to compile, under newer rules and keywords.
  • Reading old code: legacy designs use 1995-style port lists and coding habits that newer engineers may not recognize.
  • Choosing a style: most new RTL is written in SystemVerilog, but many teams keep a Verilog-2001-compatible subset for maximum tool portability.

Deep dive: the numbers and details

This part holds the standards timeline, the main language changes between versions, and code examples. Skip it if the overview is all you need.

Standards timeline

YearEvent
1980sGateway Design Automation develops Verilog with the Verilog-XL simulator
1989Cadence acquires Gateway
1990Cadence places the language in the public domain; OVI takes it forward
1995IEEE Std 1364-1995
2001IEEE Std 1364-2001 (Verilog-2001)
2005IEEE Std 1364-2005, the last stand-alone Verilog revision; IEEE Std 1800-2005, the first SystemVerilog standard
2009IEEE Std 1800-2009 merges Verilog and SystemVerilog
2023IEEE Std 1800-2023, the active standard

What Verilog-2001 changed

Verilog-2001 added features that are now taken for granted. The main ones:

  • ANSI-style port declarations: direction and type declared in the module header.
  • Combinational sensitivity shorthand: always @* instead of listing every input by hand, which removed a common source of simulation and synthesis mismatches.
  • Generate blocks with genvar for replicated hardware.
  • Signed arithmetic with the signed keyword and arithmetic shift operators <<< and >>>.
  • Multi-dimensional arrays and the comma-separated sensitivity list (@(posedge clk, posedge rst)).

The same module, 1995 style and 2001 style

// Verilog-1995 style
module mux2 (a, b, sel, y);
  input  [7:0] a, b;
  input        sel;
  output [7:0] y;
  reg    [7:0] y;
  always @(a or b or sel)
    if (sel) y = b; else y = a;
endmodule

// Verilog-2001 style
module mux2 (
  input      [7:0] a, b,
  input            sel,
  output reg [7:0] y
);
  always @* y = sel ? b : a;
endmodule

Both describe the same 8-bit, 2-to-1 multiplexer. In the 1995 version, leaving sel out of the sensitivity list would still synthesize to a mux but simulate incorrectly; always @* removes that trap.

What Verilog-2005 added

The 2005 revision was smaller. It added the uwire net type, which flags any net with more than one driver as an error, the $clog2 system function that returns the number of address bits needed for a given depth, and the `begin_keywords and `end_keywords directives that tell a tool which version's reserved words a file uses. For example, localparam AW = $clog2(1024); gives 10.

What SystemVerilog adds on top

  • Design: logic type, always_comb, always_ff and always_latch (which let tools check intent), enums, structs, packages and interfaces.
  • Verification: classes and object-oriented testbenches, constrained random stimulus, functional coverage, and SystemVerilog Assertions (SVA), which both simulators and formal tools read.
// SystemVerilog version of the same mux
module mux2 (
  input  logic [7:0] a, b,
  input  logic       sel,
  output logic [7:0] y
);
  always_comb y = sel ? b : a;
endmodule

Common mistakes when mixing versions

  • Compiling old Verilog as SystemVerilog and hitting new reserved words (for example a signal named logic or bit). The `begin_keywords directive, added in 1364-2005, lets a file declare which keyword set it was written for.
  • Assuming always @* and always_comb are identical; always_comb also runs once at time zero and lets tools flag latches.
  • Relying on simulator-specific behavior that the standard leaves undefined, such as the order of evaluation between concurrent processes.

Further reading

Share Facebook X LinkedIn WhatsApp Email

Post a Comment

0 Comments

Your comments will be moderated before it appears here.

Post a Comment (0)

#buttons=(Ok, Go it!) #days=(20)

Our website uses cookies to enhance your experience. Learn more
Ok, Go it!