Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
install [2022/04/08 09:55]
rajit
install [2023/07/09 14:04] (current)
rajit [Running large ACT files]
Line 2: Line 2:
  
 Primary development of ACT is conducted on Linux and MacOS, and so it has been extensively tested on such systems. It has also been tested in certain [[install#Microsoft Windows|Windows]] environments (see below). Primary development of ACT is conducted on Linux and MacOS, and so it has been extensively tested on such systems. It has also been tested in certain [[install#Microsoft Windows|Windows]] environments (see below).
 +
 +The core library is available from [[https://github.com/asyncvlsi/act|Github]].
 +
 +**Note:** This only installs the core circuit design tools. For those interested in the full flow, please use the [[https://github.com/asyncvlsi/actflow|actflow]] repo. The flow repository includes the core ACT repository, and includes many additional tools including ''actsim'', ''interact'', ''chp2prs'', and ''dflowmap'' (to name a few).
  
  
Line 26: Line 30:
    * Run ''./build''    * Run ''./build''
  
-If there is an issue building the software and you want to do a clean build, use ''make realclean''+If there is an issue building the software and you want to do a clean build, use ''make realclean'' before re-running the build instructions above.
  
 Once you've built the tools, run ''make install'' to install the files, and ''make runtest'' to run through a set of test cases. Once you've built the tools, run ''make install'' to install the files, and ''make runtest'' to run through a set of test cases.
Line 55: Line 59:
 ACT files are typically short since they are written by a designer. However, an ACT file generated by another program---especially if the program generates a flattened design---can be large. If an ACT process (or a namespace) has a very large number of instances/connections that are individually listed (i.e. in the input file) and the library crashes, try removing system limits on the stack size (using ''unlimit'' or ''ulimit'' depending on your shell) and re-running the program. ACT files are typically short since they are written by a designer. However, an ACT file generated by another program---especially if the program generates a flattened design---can be large. If an ACT process (or a namespace) has a very large number of instances/connections that are individually listed (i.e. in the input file) and the library crashes, try removing system limits on the stack size (using ''unlimit'' or ''ulimit'' depending on your shell) and re-running the program.
  
 +NOTE: This issue has been fixed as of 7/10/2023.
 ===== Synopsys linkages ===== ===== Synopsys linkages =====
  
 Some of the library functionality can be linked into Synopsys ''vcs'' for co-simulation support. This requires some Synopsys header files (obviously not included in the ACT distribution). Some of the library functionality can be linked into Synopsys ''vcs'' for co-simulation support. This requires some Synopsys header files (obviously not included in the ACT distribution).