forked from github/verilator
Verilator open-source SystemVerilog simulator and lint system
6ddd92c0a1
Change the Travis builds to use workspaces and persistent ccache We proceed in 2 stages (as before, but using workspaces for persistence): 1. In the 'build' stage, we clone the repo, build it and save the whole checkout ($TRAVIS_BUILD_DIR) as a workspace 2. In the 'test' stage, rather than cloning the repo, multiple jobs pull down the same workspace we built to run the tests from This enables: - Reuse of the build in multiple test jobs (this is what we used the Travis cache for before) - Each job having a separate persistent Travis cache, which now only contains the ccache. This means all jobs, including 'build' and 'test' jobs can make maximum use of ccache across runs. This drastically cuts down build times when the ccache hits, which is very often the case for 'test' jobs. Also, the separate caches only store the objects build by the particular job that owns the cache, so we can keep the per job ccache small. If the commit message contains '[travis ccache clear]', the ccache will be cleared at the beginning of the build. This can be used to test build complete within the 50 minute timeout imposed by Travis, even without a persistent ccache. |
||
---|---|---|
.github | ||
bin | ||
ci | ||
docs | ||
examples | ||
include | ||
nodist | ||
src | ||
test_regress | ||
.clang-format | ||
.clang-tidy | ||
.codacy.yml | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
Artistic | ||
Changes | ||
codecov.yml | ||
configure.ac | ||
install-sh | ||
LICENSE | ||
Makefile.in | ||
MANIFEST.SKIP | ||
README.adoc | ||
verilator-config-version.cmake.in | ||
verilator-config.cmake.in | ||
verilator.pc.in |
// Github doesn't render images unless absolute URL :!toc: ifdef::env-github[] image:https://img.shields.io/badge/License-LGPL%20v3-blue.svg[license LGPLv3,link=https://www.gnu.org/licenses/lgpl-3.0] image:https://img.shields.io/badge/License-Artistic%202.0-0298c3.svg[license Artistic-2.0,link=https://opensource.org/licenses/Artistic-2.0] image:https://api.codacy.com/project/badge/Grade/fa78caa433c84a4ab9049c43e9debc6f[Code Quality,link=https://www.codacy.com/gh/verilator/verilator] image:https://codecov.io/gh/verilator/verilator/branch/master/graph/badge.svg[Coverage,link=https://codecov.io/gh/verilator/verilator] image:https://travis-ci.com/verilator/verilator.svg?branch=master[Build Status (Travis CI),link=https://travis-ci.com/verilator/verilator] endif::[] ifdef::env-github[] :link_verilator_contributing: link:docs/CONTRIBUTING.adoc :link_verilator_install: link:docs/install.adoc endif::[] ifndef::env-github[] :link_verilator_contributing: https://github.com/verilator/verilator/blob/master/docs/CONTRIBUTING.adoc :link_verilator_install: https://verilator.org/install endif::[] :link_verilator_commercial_support: https://verilator.org/verilator_commercial_support == Welcome to Verilator [cols="a,a",indent=0,frame="none",grid="rows"] |=== ^.^| *Welcome to Verilator, the fastest Verilog/SystemVerilog simulator.* +++ <br/> +++ • Accepts synthesizable Verilog or SystemVerilog +++ <br/> +++ • Performs lint code-quality checks +++ <br/> +++ • Compiles into multithreaded {cpp}, or SystemC +++ <br/> +++ • Creates XML to front-end your own tools <.^|image:https://www.veripool.org/img/verilator_256_200_min.png[Logo,256,200] >.^|image:https://www.veripool.org/img/verilator_multithreaded_performance_bg-min.png[,388,178] ^.^| *Fast* +++ <br/> +++ • Outperforms many commercial simulators +++ <br/> +++ • Single- and multi-threaded output models ^.^| *Widely Used* +++ <br/> +++ • Wide industry and academic deployment +++ <br/> +++ • Out-of-the-box support from Arm, and RISC-V vendor IP <.^|image:https://www.veripool.org/img/verilator_usage_400x200-min.png[,400,200] >.^|image:https://www.veripool.org/img/verilator_community_400x125-min.png[,400,125] ^.^| *Community Driven & Openly Licensed* +++ <br/> +++ • Guided by the https://chipsalliance.org/[CHIPS Alliance] and https://www.linuxfoundation.org/[Linux Foundation] +++ <br/> +++ • Open, and free as in both speech and beer +++ <br/> +++ • More simulation for your verification budget ^.^| *Commercial Support Available* +++ <br/> +++ • Commercial support contracts +++ <br/> +++ • Design support contracts +++ <br/> +++ • Enhancement contracts <.^|image:https://www.veripool.org/img/verilator_support_400x125-min.png[,400,125] |=== == 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 multi-threaded .cpp and .h files, the "Verilated" code. The user writes a little {cpp}/SystemC wrapper file, which instantiates the "Verilated" model of the user's top level module. These {cpp}/SystemC files are then compiled by a {cpp} compiler (gcc/clang/MSVC++). The resulting executable performs the design simulation. Verilator also supports linking its generated libraries, optionally encrypted, into other simulators. Verilator may not be the best choice if you are expecting a full featured replacement for NC-Verilog, VCS or another commercial Verilog simulator, or if you are looking for a behavioral Verilog simulator e.g. for a quick class project (we recommend http://iverilog.icarus.com[Icarus Verilog] for this.) However, if you are looking for a path to migrate SystemVerilog to {cpp} or SystemC, or your team is comfortable writing just a touch of {cpp} code, Verilator is the tool for you. == Performance Verilator does not simply convert Verilog HDL to {cpp} or SystemC. Rather, Verilator compiles your code into a much faster optimized and optionally thread-partitioned model, which is in turn wrapped inside a {cpp}/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 http://iverilog.icarus.com[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 the closed-source Verilog simulators (Carbon Design Systems Carbonator, Modelsim, Cadence Incisive/NC-Verilog, 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 cycles/dollar. For more information on how Verilator stacks up to some of the other closed-sourced and open-sourced Verilog simulators, see the https://www.veripool.org/verilog_sim_benchmarks.html[Verilog Simulator Benchmarks]. (If you benchmark Verilator, please see the notes in the https://verilator.org/verilator_doc.pdf[Verilator manual (PDF)], and also if possible post on the forums the results; there may be additional tweaks possible.) == Installation & Documentation For more information: * {link_verilator_install}[Verilator installation and package directory structure] * https://verilator.org/verilator_doc.html[Verilator manual (HTML)], or https://verilator.org/verilator_doc.pdf[Verilator manual (PDF)] * https://github.com/verilator/verilator-announce[Subscribe to verilator announcements] * https://verilator.org/forum[Verilator forum] * https://verilator.org/issues[Verilator issues] == Support Verilator is a community project, guided by the https://chipsalliance.org/[CHIPS Alliance] under the https://www.linuxfoundation.org/[Linux Foundation]. We appreciate and welcome your contributions in whatever form; please see {link_verilator_contributing}[Contributing to Verilator]. Thanks to our https://verilator.org/verilator_doc.html#CONTRIBUTORS[Contributors and Sponsors]. Verilator also supports and encourages commercial support models and organizations; please see {link_verilator_commercial_support}[Verilator Commercial Support]. == Related Projects * http://gtkwave.sourceforge.net/[GTKwave] - Waveform viewer for Verilator traces. * http://iverilog.icarus.com[Icarus Verilog] - Icarus is a full featured interpreted Verilog simulator. If Verilator does not support your needs, perhaps Icarus may. == Open License Verilator is Copyright 2003-2020 by Wilson Snyder. (Report bugs to https://verilator.org/issues[Verilator 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.