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

Comparison of VHDL to Other Hardware Description Languages

Murugavel Ganesan
by
0
Share Facebook X LinkedIn WhatsApp Email

VHDL is a strongly typed, verbose hardware description language with a rich type system, a well-defined standard and good support for large, structured designs. Verilog is smaller and quicker to write for simple circuits, and its successor SystemVerilog adds the verification features that dominate most ASIC flows today. SystemC and other C-based approaches trade hardware precision for familiar software syntax and faster system modeling. Which one is "best" depends on the job: VHDL for strict typing and long-lived, reviewed designs; SystemVerilog for ASIC design and verification; SystemC and C++ for architecture models and high-level synthesis.

This post keeps the original 2007 comparison, updates it with the current standards, and adds side-by-side code and a summary table.

Key takeaways

  • VHDL (IEEE 1076) catches many errors at compile time through static type checking, at the cost of verbosity.
  • Verilog (IEEE 1364) is smaller and terser, but its looser rules allow simulation races that behave differently between tools.
  • Verilog has been merged into SystemVerilog (IEEE 1800) since 2009, and SystemVerilog is now the main language for ASIC verification.
  • SystemC (IEEE 1666, listed on Accellera's IEEE standards page) is a C++ class library used mainly for transaction-level models and as an input to high-level synthesis.
  • Superlog was absorbed into SystemVerilog; the language listed in the original post as "Esterelle" is Esterel, a synchronous language for control-dominated systems.

The languages in plain words

  • VHDL is careful and explicit. You declare exactly what every signal is, and the compiler refuses anything that does not fit. More typing, fewer surprises.
  • Verilog is short and quick. It trusts you, which makes small designs fast to write and some bugs easy to miss.
  • SystemVerilog is Verilog grown up: the same design style plus a full verification language with classes, random stimulus, assertions and coverage.
  • SystemC is C++ with hardware ideas added. It is used to model whole systems quickly, long before the RTL exists.

Which one should you pick?

Pick by the job and the team, not by the language. ASIC design and verification teams mostly work in SystemVerilog. FPGA, aerospace and defense projects often use VHDL. Architecture and software teams that need an early model of the chip use SystemC or C++. Most engineers end up reading at least two of these, and the core ideas (registers, combinational logic, clocks) carry over directly. The deep dive below shows the same circuit in two languages and explains the differences that matter in practice.

VHDL disadvantages

  • VHDL is verbose, complicated and can be confusing for beginners.
  • There are many different ways of saying the same thing.
  • Constructs that have a similar purpose have very different syntax, for example the sequential case statement and the concurrent selected signal assignment (with ... select).
  • Constructs that have similar syntax have very different semantics, for example variables, which update immediately, and signals, which update after a delta cycle.
  • The hardware that is synthesized is not always obvious: when a signal becomes a flip-flop, a latch or combinational logic depends on coding style, not on a keyword.

VHDL-2008 removed some of the verbosity, for example with process(all) for combinational sensitivity lists, reading of output ports, and simpler conditional statements, but tool support for the newer features has been uneven.

VHDL advantages

  • VHDL supports unsynthesizable constructs that are useful for writing high-level models, testbenches and other non-hardware artifacts needed in hardware design.
  • VHDL can be used throughout a large part of the design process in different capacities, from specification to implementation to verification.
  • VHDL has static type checking, so many errors are caught before synthesis or simulation. Assigning an 8-bit vector to a 4-bit signal is a compile error, not a silent truncation.
  • VHDL has a rich collection of data types: enumerations, records, arrays, physical types and the resolved std_logic family.
  • VHDL is a full-featured language with a good module system of libraries and packages.
  • VHDL has a well-defined standard, IEEE 1076, first published in 1987 and revised in 1993, 2000, 2002, 2008 and 2019.

Deep dive: the numbers and details

This part holds side-by-side code, the simulation race example, the language-by-language comparison with standards and dates, and a summary table. Skip it if the overview is all you need.

The same counter in VHDL and Verilog

A 4-bit counter with synchronous reset and enable shows the difference in style. First in VHDL:

library ieee;
use ieee.std_logic_1164.all;
use ieee.numeric_std.all;

entity counter4 is
  port (
    clk : in  std_logic;
    rst : in  std_logic;
    en  : in  std_logic;
    q   : out std_logic_vector(3 downto 0)
  );
end entity counter4;

architecture rtl of counter4 is
  signal count : unsigned(3 downto 0);
begin
  process (clk)
  begin
    if rising_edge(clk) then
      if rst = '1' then
        count <= (others => '0');
      elsif en = '1' then
        count <= count + 1;
      end if;
    end if;
  end process;
  q <= std_logic_vector(count);
end architecture rtl;

And in Verilog:

module counter4 (
  input  wire       clk,
  input  wire       rst,
  input  wire       en,
  output reg  [3:0] q
);
  always @(posedge clk) begin
    if (rst)
      q <= 4'd0;
    else if (en)
      q <= q + 4'd1;
  end
endmodule

The VHDL version needs an explicit conversion between unsigned and std_logic_vector. That is extra typing, but it also means the arithmetic is never ambiguous about signedness. The Verilog version is shorter, and it would also accept q + 1 with a 32-bit literal and silently truncate the result, which is fine here and a source of bugs elsewhere.

VHDL and other languages

VHDL vs Verilog

  • Verilog is a "simpler" language: it is smaller, and simple circuits are easier to write.
  • VHDL has more features than Verilog:
    • a richer set of data types and strong type checking;
    • more flexibility and expressiveness for constructing large systems, through packages, generics, configurations and records.
  • The VHDL standard is more tightly defined than the Verilog standard:
    • both VHDL and Verilog have simulation-based semantics;
    • simulation vendors generally conform closely to the VHDL standard;
    • some Verilog constructs do not simulate the same in different tools (see the race example below).
  • VHDL has traditionally been used more than Verilog in Europe and Japan, and Verilog more than VHDL in North America. South-East Asia, India and South America were more mixed. These regional patterns were the common view in 2007 and are not based on a published survey; today SystemVerilog dominates ASIC work almost everywhere, while VHDL remains strong in FPGA, aerospace and defense.

Why Verilog can simulate differently in different tools The Verilog standard lets a simulator run always blocks that trigger on the same event in any order. With blocking assignments that creates a race:

// Race: the result depends on which block the simulator runs first
always @(posedge clk) a = b;
always @(posedge clk) b = a;

One simulator may end with both signals equal to the old b, another with both equal to the old a. Using nonblocking assignments for sequential logic removes the race, because all right-hand sides are read before any left-hand side is updated:

module swap_nb (
  input  wire clk,
  input  wire load,
  output reg  a,
  output reg  b
);
  always @(posedge clk) if (load) a <= 1'b1; else a <= b;
  always @(posedge clk) if (load) b <= 1'b0; else b <= a;
endmodule

After loading, a and b swap on every clock edge in any compliant simulator. VHDL avoids this class of problem by design: signals always update after a delta cycle, so the equivalent VHDL code cannot race.

VHDL vs SystemC

  • SystemC looks like C++, so the syntax is familiar to software engineers.
  • C is often used for algorithmic descriptions of circuits, so why not use it for synthesizable code as well? That is the idea behind high-level synthesis (HLS).
  • If you think VHDL is hard to synthesize, try C. Pointers, dynamic memory and unbounded loops have no direct hardware meaning, so synthesizable C and SystemC are restricted subsets with tool-specific rules.
  • SystemC simulation is slower than advertised when written at signal and clock level. Its real speed advantage comes from transaction-level modeling (TLM), where a whole bus transfer is a single function call.

SystemC is standardized as IEEE 1666, with the latest revision published in 2023. Today it is used mainly for virtual prototypes, architecture exploration and as one of the inputs to HLS tools, rather than as a replacement for RTL.

VHDL vs other hardware description languages

  • Superlog: a proposed language based on Verilog and C. Its core came from Verilog, with C-like extensions to make the language more expressive and powerful. It was developed by Co-Design Automation, which Synopsys acquired in 2002, and is no longer developed. Superlog was superseded by SystemVerilog.
  • SystemVerilog: originally built on the Superlog donation from Co-Design and standardized first by Accellera, an organization that standardizes EDA languages, and then by the IEEE as IEEE 1800-2005. It draws on Verilog, Superlog, Vera and SystemC ideas. SystemVerilog is a superset of Verilog aimed at both high-level design and verification, and since IEEE 1800-2009 the Verilog standard has been merged into it. The current edition is IEEE 1800-2023.
  • Esterel (spelled "Esterelle" in the original post): a synchronous language that moved from academia (French research groups including INRIA) to commercial use. It has very clean semantics, is aimed at state machines and control logic, and has limited support for datapath operations.

Newer options since 2007 Several languages have appeared since this post was first written. Chisel (embedded in Scala, used for many RISC-V cores), SpinalHDL and Amaranth (Python) generate Verilog from a general-purpose programming language. Bluespec SystemVerilog uses rules and guarded atomic actions. HLS from C++ is widely used for signal processing and accelerators. All of them still produce Verilog or VHDL for the downstream tools.

Summary comparison

LanguageStandardTypingMain strengthsMain uses today
VHDLIEEE 1076 (latest 2019)Strong, staticType safety, packages, deterministic simulationFPGA, aerospace, defense, European industry
VerilogIEEE 1364-2005, merged into IEEE 1800WeakSmall, terse, fast to writeLegacy RTL, netlists, tool interchange
SystemVerilogIEEE 1800 (latest 2023)Mixed, stronger than VerilogVerification features: classes, constraints, assertions, coverageASIC design and verification (UVM)
SystemCIEEE 1666 (latest 2023)C++ typesFast transaction-level models, C++ ecosystemVirtual prototypes, architecture models, HLS
EsterelNo IEEE standardOwn type systemClean synchronous semantics for controlNiche: control-dominated and safety-critical software and hardware

Frequently asked questions

Should a beginner learn VHDL or Verilog first? For an ASIC career, Verilog and then SystemVerilog are the more common starting point. For FPGA, defense or aerospace work, VHDL is often required. The underlying ideas of registers, combinational logic and timing are the same, so the second language is much easier than the first.

Is Verilog still a separate standard? No. IEEE 1364-2005 was the last separate Verilog standard. Since 2009 Verilog has been part of the SystemVerilog standard, IEEE 1800.

Can VHDL and Verilog be mixed in one design? Yes. Most commercial simulators and synthesis tools support mixed-language designs, though care is needed at the boundary with type mapping and parameters or generics.

Is SystemC a hardware description language? It is a C++ library that can describe hardware. It is used more for system-level and transaction-level models than for RTL, although HLS tools accept synthesizable SystemC.

Further reading

Murugavel Ganesan
About the Author
Murugavel Ganesan
Product Director | SerDes · IVN · Edge AI · Compute | Ex Intel · Infineon

A semiconductor product leader working across product architecture, definition, strategy, and silicon and software execution, from concept through volume production. He has worked with teams across Asia, Europe and the USA, including at Intel, Infineon and ArrayComm.

His work covers ASICs, SoCs, FPGAs and chiplets for wireless, wireline, automotive, IoT and AI, including PCIe, CXL and DDR interfaces alongside RF and mixed-signal design.

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!