Verilator open-source SystemVerilog simulator and lint system
Go to file
Jeffrey Song 09e20633bb Keep task variables activation-local across forks
Context:
Task inlining lowered automatic task arguments, locals, and output staging temporaries into object-scope storage. Concurrent activations from one call site could then share state. Keeping declarations lexical exposed dangling AstVarScope links when statement subtrees were cloned by unrolling, splitting, or scheduler replication.

Changes:
- Represent activation-local declarations with a transient AstTaskLocalVar whose scoped template survives statement cloning.
- Materialize independent local variables and scopes immediately after loop unrolling, including references captured by nested task activations.
- Move single-color V3Split leaves instead of cloning them, preserving external lexical-scope links without changing split membership.
- Use activation-local storage only for task bodies that can suspend or fork, leaving non-suspending task and function paths unchanged.
- Keep timing sensitivity temporaries in their nearest lexical CLocalScope.
- Relink scheduler logic clones to independent AstVarScopes and remove only unreferenced scopes whose cloned declarations were discarded.
- Cover input, local, output, inout, nested capture, unroll, split, scheduler replication, and AST tree/JSON dump paths.

Evidence:
- Before the fix, the unroll, nested-split, dynamic-process, and scheduler-replication reproducers fail --debug-check with broken or dangling local links.
- The final focused task/fork set passes 31/31 vlt/vltmt scenarios.
- Scheduler/ICO and fork/timing-fork regression groups pass; the sole initial FST failure passes after supplying the Homebrew lz4 include and library paths.
- make format completes with clang-format 18; git diff --check passes.
- make cppcheck and make lint-py exit successfully; lint-py reports only the existing macOS sched_getaffinity mypy diagnostic.

Boundary:
This changes activation-local task lowering and ownership-preserving cloning of task-local declarations. It does not change disable-fork process-queue semantics, non-suspending function storage, or scheduler region assignment.
2026-07-13 06:03:03 -07:00
.devcontainer Tests: Untabify some tests. 2024-09-01 21:12:37 -04:00
.github CI: Disable ccache on coverage jobs (#7887) 2026-07-06 17:05:14 +01:00
LICENSES Commentary: Changes update 2026-05-12 09:52:18 -04:00
bin Support dynamic loading of VPI extensions (#7727) 2026-06-28 09:28:09 -04:00
ci Add --enable-light-debug configure option (#7886) 2026-07-06 18:02:37 +01:00
docs Tests: Add TSan and failing multi-threaded data race test (#7913) 2026-07-10 14:34:51 +01:00
examples Add SPDX copyright identifiers, and get 'reuse' clean. No functional change. 2026-01-26 20:24:34 -05:00
include Fix scoped randomize with array members under rand_mode (#7877) 2026-07-11 20:28:49 -07:00
nodist Internals: Fix lint-py warning 2026-06-07 21:37:16 -04:00
src Keep task variables activation-local across forks 2026-07-13 06:03:03 -07:00
test_regress Keep task variables activation-local across forks 2026-07-13 06:03:03 -07:00
.bake.toml Add SPDX copyright identifiers, and get 'reuse' clean. No functional change. 2026-01-26 20:24:34 -05:00
.clang-format Fix header order botched by clang-format in recent commit. 2023-10-18 06:37:46 -04:00
.clang-tidy Internals: Suppress clang-tidy warnings in macros (#7656) 2026-05-27 05:16:49 -07:00
.codacy.yml CI: Avoid duplicate action runs on dependabot 2025-09-03 18:54:27 -04:00
.codecov.yml Add SPDX copyright identifiers, and get 'reuse' clean. No functional change. 2026-01-26 20:24:34 -05:00
.gitattributes Commentary: Convert Changes to RST format 2021-03-14 14:12:58 -04:00
.gitignore Add 'make venv' target (#6775) 2025-12-14 11:18:32 +00:00
.pre-commit-hooks.yaml Add Docker pre-commit hook (#5238) (#5452) 2024-09-23 07:37:24 -04:00
.style.yapf Internals: Add .style.yapf 2024-08-26 21:53:36 -04:00
AGENTS.md CI: Autoformat markdown files 2026-06-15 17:44:50 -04:00
CITATION.cff Internals: Format CITATION.cff as proper YAML 2025-12-20 22:19:15 -05:00
CMakeLists.txt devel release 2026-07-01 18:31:23 -04:00
CPPLINT.cfg Internals: Add cpplint control file and related cleanups 2022-01-09 16:49:38 -05:00
Changes Commentary: Changes update 2026-07-10 08:43:12 -04:00
LICENSE Add back LICENSE file due to (f4pga/actions#49) 2026-02-02 19:34:10 -05:00
Makefile.in CI/Makefile: Auto format .rst files (#7816) 2026-06-21 13:53:00 -04:00
README.rst Commentary: Make RST documents round-trip clean. No output change intended. 2026-06-21 10:15:47 -04:00
REUSE.toml Commentary: Changes update 2026-05-12 09:52:18 -04:00
configure.ac Tests: Add TSan and failing multi-threaded data race test (#7913) 2026-07-10 14:34:51 +01:00
install-sh Internals: Avoid using <tab> in the middle of lines (#3913) 2023-01-29 22:39:22 -05:00
python-dev-requirements.txt CI: Cache Python venv (#7879) 2026-07-06 11:03:35 +01:00
verilator-config-version.cmake.in Add SPDX copyright identifiers, and get 'reuse' clean. No functional change. 2026-01-26 20:24:34 -05:00
verilator-config.cmake.in Support new FST writer API (#6871) (#6992) 2026-05-12 07:39:43 -04:00
verilator.pc.in Fix default pkgconfig version to have no spaces (#2308) 2020-05-05 08:46:24 -04:00

README.rst

..
   Github doesn't render images unless absolute URL
   Do not know of a conditional tag, "only: github" nor "github display" works
   SPDX-FileCopyrightText: 2003-2026 Wilson Snyder
   SPDX-License-Identifier: LGPL-3.0-only OR Artistic-2.0

|badge1| |badge2| |badge3| |badge4| |badge5| |badge7| |badge8|

.. |badge1| image:: https://img.shields.io/badge/Website-Verilator.org-181717.svg
   :target: https://verilator.org

.. |badge2| image:: https://img.shields.io/badge/License-LGPL%20v3-blue.svg
   :target: https://www.gnu.org/licenses/lgpl-3.0

.. |badge3| image:: https://img.shields.io/badge/License-Artistic%202.0-0298c3.svg
   :target: https://opensource.org/licenses/Artistic-2.0

.. |badge4| image:: https://repology.org/badge/tiny-repos/verilator.svg?header=distro%20packages
   :target: https://repology.org/project/verilator/versions

.. |badge5| image:: https://img.shields.io/docker/pulls/verilator/verilator
   :target: https://hub.docker.com/r/verilator/verilator

.. |badge7| image:: https://github.com/verilator/verilator/workflows/build/badge.svg
   :target: https://github.com/verilator/verilator/actions?query=workflow%3Abuild

.. |badge8| image:: https://img.shields.io/github/actions/workflow/status/verilator/verilator/rtlmeter.yml?branch=master&event=schedule&label=benchmarks
   :target: https://verilator.github.io/verilator-rtlmeter-results

Welcome to Verilator
====================

.. list-table::

   - - **Welcome to Verilator, the fastest Verilog/SystemVerilog simulator.**
          - Accepts Verilog or SystemVerilog
          - Performs lint code-quality checks
          - Compiles into multithreaded C++, or SystemC
          - Creates JSON to front-end your own tools
     - |Logo|
   - - |verilator multithreaded performance|
     - **Fast**
          - Outperforms many closed-source commercial simulators
          - Single- and multithreaded output models
   - - **Widely Used**
          - Wide industry and academic deployment
          - Out-of-the-box support from Arm and RISC-V vendor IP
          - Over 700 contributors
     - |verilator usage|
   - - |verilator community|
     - **Community Driven & Openly Licensed**
          - Guided by the `CHIPS Alliance`_ and `Linux Foundation`_
          - Open, and free as in both speech and beer
          - More simulation for your verification budget
   - - **Commercial Support Available**
          - Commercial support contracts
          - Design support contracts
          - Enhancement contracts
     - |verilator support|

What Verilator Does
===================

Verilator is invoked with parameters similar to GCC or Synopsys's VCS. It
"Verilates" the specified Verilog or SystemVerilog code by reading it,
performing lint checks, and optionally inserting assertion checks and
coverage-analysis points. It outputs single- or multithreaded .cpp and .h
files, the "Verilated" code.

Verilator can automatically generate a simulator executable (using
``--binary``), or users can write their own C++/SystemC wrapper to
instantiate the model. The resulting Verilated executable performs the
design simulation. Verilator also supports linking Verilator-generated
libraries, optionally encrypted, into other simulators.

Verilator supports all design constructs, most verification constructs,
intra-assignment delays (e.g, `#10`), and events. Tristate-bus (`z`) and
unknowns (`x`) are handled in limited contexts, in a special manor for
performance. It currently may not be the best choice if you are expecting a
full-featured replacement for a closed-source Verilog simulator, performing
SDF annotation, or mixed-signal simulation. However, if you are looking for
a path to migrate SystemVerilog to C++/SystemC, or want high-speed
simulation, Verilator is the tool for you.

Performance
===========

Verilator does not directly translate Verilog HDL to C++ or SystemC.
Rather, Verilator compiles your code into a much faster optimized and
optionally thread-partitioned model, which is in turn wrapped inside a
C++/SystemC module. The results are a compiled Verilog model that executes
even on a single thread over 10x faster than standalone SystemC, and on a
single thread is about 100 times faster than interpreted Verilog simulators
such as `Icarus Verilog`_. Another 2-10x speedup might be gained from
multithreading (yielding 200-1000x total over interpreted simulators).

Verilator has typically similar or better performance versus closed-source
Verilog simulators (e.g., Aldec Riviera-Pro, Cadence Incisive/NC-Verilog,
Mentor ModelSim/Questa, Synopsys VCS, VTOC, and Pragmatic CVer/CVC). But,
Verilator is open-sourced, so you can spend on computes rather than
licenses. Thus, Verilator gives you the best simulation cycles/dollar.

Installation & Documentation
============================

For more information:

- `Verilator installation and package directory structure
  <https://verilator.org/install>`_

- `Verilator manual (HTML) <https://verilator.org/verilator_doc.html>`_, or
  `Verilator manual (PDF) <https://verilator.org/verilator_doc.pdf>`_

- `Subscribe to Verilator announcements
  <https://github.com/verilator/verilator-announce>`_

- `Verilator forum <https://verilator.org/forum>`_

- `Verilator issues <https://verilator.org/issues>`_

Support
=======

Verilator is a community project, guided by the `CHIPS Alliance`_ under the
`Linux Foundation`_.

We appreciate and welcome your contributions in whatever form; please see
`Contributing to Verilator
<https://github.com/verilator/verilator/blob/master/docs/CONTRIBUTING.rst>`_.
Thanks to our `Contributors and Sponsors
<https://verilator.org/guide/latest/contributors.html>`_.

Verilator also supports and encourages commercial support models and
organizations; please see `Verilator Commercial Support
<https://verilator.org/verilator_commercial_support>`_.

Related Projects
================

- `Cocotb <https://www.cocotb.org/>`_ - A coroutine-based cosimulation
  library for writing testbenches in Python which officially supports
  Verilator.

- `GTKwave <https://gtkwave.sourceforge.net/>`_ - Waveform viewer for
  Verilator traces.

- `Icarus Verilog`_ - Icarus is a highly-featured interpreted Verilog
  simulator. If Verilator does not support your needs, perhaps Icarus may.

- `Surfer <https://surfer-project.org/>`_ - Web or offline waveform viewer
  for Verilator traces.

Open License
============

Verilator is Copyright 2003-2026 by Wilson Snyder. (Report bugs to
`Verilator Issues <https://verilator.org/issues>`_.)

Verilator is free software; you can redistribute it and/or modify it under
the terms of either the GNU Lesser General Public License Version 3 or the
Perl Artistic License Version 2.0. See the documentation for more details.

.. _chips alliance: https://chipsalliance.org

.. _icarus verilog: https://steveicarus.github.io/iverilog

.. _linux foundation: https://www.linuxfoundation.org

.. |Logo| image:: https://www.veripool.org/img/verilator_256_200_min.png

.. |verilator multithreaded performance| image:: https://www.veripool.org/img/verilator_multithreaded_performance_bg-min.png

.. |verilator usage| image:: https://www.veripool.org/img/verilator_usage_400x200-min.png

.. |verilator community| image:: https://www.veripool.org/img/verilator_community_400x125-min.png

.. |verilator support| image:: https://www.veripool.org/img/verilator_support_400x125-min.png