Download Compiler, Standard Library and Demos
1 Compiler: the sac2c ecosystem
| ||April 26, 2017||MacOS, DEB7, DEB8, RHEL6, RHEL7, TGZ||Includes CUDA and HWLOC support|
We also have some user-contributed packages: ArchLinux (AUR)
Releases have been tested on specific operating system versions. Though some packages can be installed on newer or older systems, we advise against doing this. If you find a problem, please contact us via the information further below.
RPM (RedHat Based distributions)
rpm release of the compiler is designed to be installed on RedHat based distributions of Linux (e.g. RedHat, CentOS, Fedora, etc.) using the
rpm tool set.
$ sudo rpm --install sac2c-VERSION-RELEASE.rpm
DEB (Debian based distributions)
deb package is meant to be installed on Debian based distributions (e.g. Debian, Ubuntu, etc.) using the
dpkg tool set.
$ sudo dpkg --install sac-VERSION-RELEASE.deb
Pkg (Apple MacOS)
pkg is a installer that will place the SaC files in the correct location on your system. Symbolic links to the SaC binaries are created in
/usr/local/bin for your convenience.
The SaC binaries are postfixed by their release type (production or debug), so there is a
sac2c is simply a link to
- Double click the downloaded
- A dialog box should appear that will guide you through the install process
- Confirm that you agree with our license, and click Install to install SaC
- The binary
sac2c_pshould be in your
TAR.GZ (Unix-like operating systems)
.tar.gz archive is the most basic distributable package that available. The archive contains the entire directory structure of the binaries and libraries as they should appear on the file-system of the host from the root directory (i.e.
/). The default directory structure is prefixed with
Installation of the compiler is as simple as extracting from the archive:
$ sudo tar --strip-components=1 -C / -xzf sac2c-VERSION-RELEASE.tar.gz
Interested in contributing to the project? You can do so in several ways, by either telling us about bugs or by contributing code to the project.
Head over to the community page and follow the guidelines there on how to submit a bug.
2 Standard Library: SacBase
The standard library comes as a collection of public repositories on github/SacBase.
As a minimum you should consider getting the core stdlib, either in binary form or as source code from SacBase/Stdlib.
In the case of the source code, you'll have to check out the latest versions of the the
stdlib repository and possibly further repositories from
SacBase, you need to build and install the standard library.
Normally, the install of the stdlib should work fine in which case may want to proceed to the
If you are curious about the details on where the built modules are actually stored or on how platform dependent versions are created and kept apart you can read up about cross compilation and the SBI (SaC Binary Interface).