Version v8.2.0-2.2-20190521 is a maintenance release of GNU MCU Eclipse RISC-V Embedded GCC, that fixes the previous bug affecting GDB on macOS.

Binary files »


Starting with v8.2.0-2, this distribution closely follows the official SiFive Freedom Tools distribution.

This release is similar to the SiFive 2019-02 release, including support for SiFive specific CLIC interrupts.

The following commits were used:

GDB was upstreamed and does not require SiFive specific patches, so the current build uses git://, the c8aa0bb commit from 28 Feb 2019.


All architectures, ABIs and libraries supported by the riscv64-unknown-elf toolchain are also supported, with the following improvements:

  • a newer newlib was included, which supports the ‘underscore’ syscall functions
  • the mandatory reference to libgloss in the linker configuration was removed
  • the march=rv32imaf/mabi=ilp32f library was added to the list of multi-libs
  • support for newlib-nano was added
  • the standard documentation, in PDF and HTML, was added


Binaries for Windows, macOS and GNU/Linux are provided.

The GNU/Linux binaries were built on two CentOS 6 Docker images (32/64-bit), and run on any distribution based on CentOS 6 or later.

The Windows binaries were built with mingw-w64, and run on any reasonably recent i686 and x86_64 Windows machines.

Instructions on how to install the binaries are available in the How to install the RISC-V toolchain? page.

The toolchain is also available as an xPack and can be conveniently installed with xpm:

xpm install --global @gnu-mcu-eclipse/riscv-none-gcc

This installs the latest available version.

For better control and repeatability, the build scripts use Docker containers; all files required during builds are available as a separate gnu-mcu-eclipse/riscv-none-gcc-build project.


The binaries were testes on Windows 10 Pro 32/64-bit, Ubuntu 18 LTS 64-bit, Xubuntu 18 LTS 32-bit and macOS 10.13.

The tests consist in building and debugging some simple Eclipse projects available in the build project.

Since the source code used for GCC is identical to the one used by SiFive, the long and complex tests performed by SiFive to validate their release were not executed again.

Known problems

  • none (so far).


The SHA-256 hashes for the files are: