3
0
Fork 0
mirror of https://github.com/YosysHQ/yosys synced 2026-06-05 00:20:52 +00:00
No description
Find a file
Miodrag Milanović d7093743b8
Merge pull request #5932 from YosysHQ/cmake_fixes
Populate link_flags in yosys-config
2026-06-04 11:10:02 +00:00
.github Bump CI to use gcc-16 as latest compiler 2026-06-03 13:09:38 +02:00
abc@5d51a5e420 Update ABC as per 2026-05-12 2026-05-12 08:37:44 +02:00
backends Merge pull request #5894 from YosysHQ/gcc_16 2026-06-03 12:07:45 +00:00
cmake Merge pull request #5932 from YosysHQ/cmake_fixes 2026-06-04 11:10:02 +00:00
docs docs: Resolving todos 2026-06-04 20:35:52 +12:00
examples Migrate build system to CMake 2026-06-03 08:58:10 +00:00
frontends Merge pull request #5903 from YosysHQ/krys/verific_memsize 2026-06-04 05:43:04 +00:00
guidelines Fix typos in GettingStarted 2026-04-02 10:23:13 -05:00
kernel Fix compile with VisualStudio 2026-06-04 12:25:41 +02:00
libs Fix Windows portability issues that break MSVC build. 2026-06-03 08:58:11 +00:00
misc Migrate build system to CMake 2026-06-03 08:58:10 +00:00
nix Migrate build system to CMake 2026-06-03 08:58:10 +00:00
passes Merge pull request #5903 from YosysHQ/krys/verific_memsize 2026-06-04 05:43:04 +00:00
pyosys Update top-level Python project for CMake compatibility. 2026-06-03 09:03:23 +00:00
techlibs Migrate build system to CMake 2026-06-03 08:58:10 +00:00
tests Merge pull request #5903 from YosysHQ/krys/verific_memsize 2026-06-04 05:43:04 +00:00
.clang-format split CodingReadme into multiple files 2021-03-22 19:16:25 +01:00
.dockerignore split CodingReadme into multiple files 2021-03-22 19:16:25 +01:00
.editorconfig docs: write small guide for using pyosys 2025-10-03 11:54:44 +03:00
.gitattributes Make GIT_REV logic work in release tarballs 2022-05-25 11:20:09 +02:00
.gitcommit Makefile: reproducible .gitcommit 2024-07-12 10:52:03 +02:00
.gitignore Tidy up install instructions 2026-06-04 20:34:52 +12:00
.gitmodules actions: vendor sources with submodules for releases 2024-10-17 00:11:10 +02:00
.mailmap mailmap: fix up some identities. 2025-01-29 01:39:09 +01:00
.readthedocs.yaml RTDs: Fail on warning 2024-09-03 10:20:24 +12:00
Brewfile Update CI scripts for CMake 2026-06-03 08:58:11 +00:00
CHANGELOG Next dev cycle 2026-06-01 18:23:28 +02:00
CMakeLists.txt CMake: Add wrapper for test-docs 2026-06-04 20:35:51 +12:00
CODE_OF_CONDUCT.md CODE_OF_CONDUCT now explicitly .md 2024-12-05 09:21:13 +13:00
CODEOWNERS pyosys: rewrite using pybind11 2025-10-03 11:54:44 +03:00
CONTRIBUTING.md contributing: small responses to feedback 2026-04-07 18:59:06 +02:00
COPYING Release version 0.61 2026-01-13 08:35:02 +01:00
flake.lock Migrate build system to CMake 2026-06-03 08:58:10 +00:00
flake.nix Migrate build system to CMake 2026-06-03 08:58:10 +00:00
pyproject.toml Update top-level Python project for CMake compatibility. 2026-06-03 09:03:23 +00:00
README.md docs: Resolving todos 2026-06-04 20:35:52 +12:00

yosys Yosys Open SYnthesis Suite

This is a framework for RTL synthesis tools. It currently has extensive Verilog-2005 support and provides a basic set of synthesis algorithms for various application domains.

Yosys can be adapted to perform any synthesis job by combining the existing passes (algorithms) using synthesis scripts and adding additional passes as needed by extending the yosys C++ code base.

Yosys is free software licensed under the ISC license (a GPL compatible license that is similar in terms to the MIT license or the 2-clause BSD license).

Third-party software distributed alongside this software is licensed under compatible licenses. Please refer to abc and libs subdirectories for their license terms.

Web Site and Other Resources

More information and documentation can be found on the Yosys web site:

If you have any Yosys-related questions, please post them on the Discourse group:

Documentation from this repository is automatically built and available on Read the Docs:

Users interested in formal verification might want to use the formal verification front-end for Yosys, SBY:

The Yosys blog has news and articles from users:

Installation

Yosys is part of the Tabby CAD Suite and the OSS CAD Suite! The easiest way to use yosys is to install the binary software suite, which contains all required dependencies and related tools.

Make sure to get a Tabby CAD Suite Evaluation License if you need features such as industry-grade SystemVerilog and VHDL parsers!

For more information about the difference between Tabby CAD Suite and the OSS CAD Suite, please visit https://www.yosyshq.com/tabby-cad-datasheet

Many Linux distributions also provide Yosys binaries, some more up to date than others. Check with your package manager!

Building from Source

For more details, and instructions for other platforms, check building from source on Read the Docs.

When cloning Yosys, some required libraries are included as git submodules. Make sure to call e.g.

$ git clone --recurse-submodules https://github.com/YosysHQ/yosys.git

or

$ git clone https://github.com/YosysHQ/yosys.git
$ cd yosys
$ git submodule update --init --recursive

A C++ compiler with C++20 support is required as well as some standard tools such as GNU Flex, GNU Bison (>=3.8), CMake (>=3.27), Make (or other CMake generator such as Ninja), and Python (>=3.11). Some additional tools: readline, libffi, Tcl and zlib; will be used if available but are optional. Graphviz and Xdot are used by the show command to display schematics.

For example on Ubuntu Linux 22.04 LTS the following commands will install all prerequisites for building yosys:

$ sudo apt-get install gawk git make python3 lld bison clang flex \
	libffi-dev libfl-dev libreadline-dev pkg-config tcl-dev zlib1g-dev \
	graphviz xdot

NOTE: By default, Ubuntu 22.04 LTS is limited to CMake 3.22 via apt. To install a newer version and meet the minimum required for building Yosys, use sudo snap install cmake --classic.

CMake is used for build configuration, and requires a separate build directory:

$ cmake -B build .

Once generated, available build variables can be inspected and modified with ccmake or opening the generated build/CMakeCache.txt file:

$ ccmake build              #..or..
$ vi build/CMakeCache.txt

When setting one-off variables, CMake provides the -D <var>=<value> command line option. For example, disabling zlib support:

$ cmake -B build . -DYOSYS_WITHOUT_ZLIB=ON

For a more persistent configuration, we recommend creating and using a CMakeUserPresets.json file in the root yosys directory. Below is an example file which enables ccache and sets the default compiler to clang when calling cmake --preset clang:

{
	"version": 1,
	"configurePresets": [
		{
			"name": "default",
			"binaryDir": "build",
			"generator": "Unix Makefiles",
			"cacheVariables": {
				"CMAKE_C_COMPILER": "clang",
				"CMAKE_CXX_COMPILER": "clang++",
				"YOSYS_COMPILER_LAUNCHER": "ccache"
			}
		}
	]
}

Once generated, the build system can be run as follows:

$ cmake --build build       #..or..
$ cd build
$ cmake --build .

To quickly install Yosys with the default settings:

$ cmake -B build . -DCMAKE_BUILD_TYPE=Release
$ cmake --build build --config Release --parallel $(nproc)
$ sudo cmake --install build --strip

Tests are located in the tests subdirectory and can be executed using the test target. Note that you need gawk, a recent version of iverilog, and gtest. Execute tests via:

$ cmake --build build --target test --parallel $(nproc)

Getting Started

Yosys can be used with the interactive command shell, with synthesis scripts or with command line arguments. Let's perform a simple synthesis job using the interactive command shell:

$ ./build/yosys
yosys>

the command help can be used to print a list of all available commands and help <command> to print details on the specified command:

yosys> help help

reading and elaborating the design using the Verilog frontend:

yosys> read -sv tests/simple/fiedler-cooley.v
yosys> hierarchy -top up3down5

writing the design to the console in the RTLIL format used by Yosys internally:

yosys> write_rtlil

convert processes (always blocks) to netlist elements and perform some simple optimizations:

yosys> proc; opt

display design netlist using xdot:

yosys> show

the same thing using gv as postscript viewer:

yosys> show -format ps -viewer gv

translating netlist to gate logic and perform some simple optimizations:

yosys> techmap; opt

write design netlist to a new Verilog file:

yosys> write_verilog synth.v

or using a simple synthesis script:

$ cat synth.ys
read -sv tests/simple/fiedler-cooley.v
hierarchy -top up3down5
proc; opt; techmap; opt
write_verilog synth.v

$ ./yosys synth.ys

If ABC is enabled in the Yosys build configuration and a cell library is given in the liberty file mycells.lib, the following synthesis script will synthesize for the given cell library:

# read design
read -sv tests/simple/fiedler-cooley.v
hierarchy -top up3down5

# the high-level stuff
proc; fsm; opt; memory; opt

# mapping to internal cell library
techmap; opt

# mapping flip-flops to mycells.lib
dfflibmap -liberty mycells.lib

# mapping logic to mycells.lib
abc -liberty mycells.lib

# cleanup
clean

If you do not have a liberty file but want to test this synthesis script, you can use the file examples/cmos/cmos_cells.lib from the yosys sources as simple example.

Liberty file downloads for and information about free and open ASIC standard cell libraries can be found here:

The command synth provides a good default synthesis script (see help synth):

read -sv tests/simple/fiedler-cooley.v
synth -top up3down5

# mapping to target cells
dfflibmap -liberty mycells.lib
abc -liberty mycells.lib
clean

The command prep provides a good default word-level synthesis script, as used in SMT-based formal verification.

Additional information

The read_verilog command, used by default when calling read with Verilog source input, does not perform syntax checking. You should instead lint your source with another tool such as Verilator first, e.g. by calling verilator --lint-only.

Building the documentation

Note that there is no need to build the manual if you just want to read it. Simply visit https://yosys.readthedocs.io/en/latest/ instead. If you're offline, you can read the sources, replacing .../en/latest with docs/source.

In addition to those packages listed above for building Yosys from source, the following are used for building the website:

$ sudo apt install pdf2svg faketime

Or for MacOS, using homebrew:

$ brew install pdf2svg libfaketime

PDFLaTeX, included with most LaTeX distributions, is also needed during the build process for the website. Or, run the following:

$ sudo apt install texlive-latex-base texlive-latex-extra latexmk

Or for MacOS, using homebrew:

$ brew install basictex
$ sudo tlmgr update --self
$ sudo tlmgr install collection-latexextra latexmk tex-gyre

The Python package, Sphinx, is needed along with those listed in docs/source/requirements.txt:

$ pip install -U sphinx -r docs/source/requirements.txt

DOCS (e.g.)

$ cmake --build build --target docs-html --parallel

This will build/rebuild yosys as necessary before generating the website documentation from the yosys help commands. To build for pdf instead of html, use the docs-latexpdf target.