Home
This is the iverilog GIT repository.
If you are looking for the main Icarus Verilog documentation, look here: https://steveicarus.github.io/iverilog/
There are various trans branches around, for different purposes, but the version branches are those that reflect the versions available. It is preferred that one not commit directly to the version branches, but instead create PR's that are merged. In fact, only the core maintainers are even allowed to commit or merge to these branches, so the general plan is to create a branch that you work in, then create a PR off a version branch to arrange for your branch to be merged.
When you get a "git clone", you are generally dropped in the "master" branch. to creat a locak tracking branch of one of the version branches, use a command like this (assuming that "origin" is the name you gave to the remote):
% git checkout --track -b v11-branch origin/v11-branch
This is the main development branch and is the default branch when you do a git clone and don't otherwise switch to a branch. Mot development happens here. The master branch does not have vNN_N tags, but instead has sYYYYMMD snapshot tags.
- s20221226 - First snapshot after the v12 split.
This is the branch for the stable v12 release. Bug fixes to the stable release are put here, and minor releases are tags on this branch.
- v12_0 - Initial release of v12 stable. This is the start of the branch.
This is the branch for the stable v11 release.
This is the branch for the stable v10 release. V10 is now obsolete. You should be using V11 if you need a stable version.