Valgrind Home Information Source Code Documentation Contact How to Help Gallery

Supported Platforms


Valgrind supports the following platforms:

  • x86/Linux: up to and including SSSE3, but not higher -- no SSE4, AVX, AVX2. This target is in maintenance mode now..
  • AMD64/Linux: up to and including AVX2. This is the primary development target and tends to be well supported.
  • PPC32/Linux, PPC64/Linux, PPC64LE/Linux: up to and including Power8.
  • S390X/Linux: supported.
  • ARM/Linux: up to and including ARMv7.
  • ARM64/Linux: Up to and including ARMv8.
  • MIPS32/Linux, MIPS64/Linux: supported.
  • X86/Solaris, AMD64/Solaris, X86/illumos, AMD64/illumos: support is new in 3.11.0.
  • X86/Darwin (10.10, 10.11), AMD64/Darwin (10.10, 10.11): supported.
  • ARM/Android, ARM64/Android, MIPS32/Android, X86/Android: supported.

On Linux, you must be running kernel 3.0 or later, and glibc 2.5.X or later. On Mac OS X you must be running 10.9.x or later.

For details of which distributions the current release (valgrind-3.11.0) builds and runs its regression tests on, see the release notes.

Out Of Tree

The following ports have been done and are maintained outside the Valgrind repository. Note that they may have varying levels of completeness, may not work reliably, and may target older versions of Valgrind.

  • x86/FreeBSD
    Doug Rabson and others haved done a fairly complete port of Valgrind 3.X. The FreeBSD porting team actively maintains the port. Snapshots of the work in progress are at this FreeBSD page.

  • x86/NetBSD
    Eric Auge, Kailash Sethuraman and Peter Bex are doing a port of Valgrind 3.X, available at this page.

  • sparcv9/Solaris
    The port of Valgrind on sparcv9/Solaris is currently in progress. The code is available at this page. There are still many challenges ahead and a lot of work to do.

Porting Plans

Valgrind 3.X has the infrastructure to support multiple platforms. A platform is a specific (CPU,OS) pairing, such as x86/Linux or AMD64/Linux.

Maintaining each port takes a lot of effort, more so than for most other programs. Valgrind is fragile due to the low-level nature of what it does. Also, each platform port has CPU-specific code, OS-specific code and platform-specific code, and testing all the combinations is difficult.

Because of this, we can only justify supporting platforms that are widely used. Unlike NetBSD or GCC, we are not interested in having Valgrind work on every platform in the known universe: the maintenance burden is too high. Therefore, porting Valgrind to different platforms is not simply a technical exercise: you also need to make a convincing case that the effort will be worth it, and that the port will be supported properly, at least in the foreseeable future.

Windows is not under consideration because porting to it would require so many changes it would almost be a separate project. (However, Valgrind + Wine can be made to work with some effort.) Also, non-open-source OSes are difficult to deal with; being able to see the OS and associated (libc) source code makes things much easier. However, Valgrind is quite usable in conjunction with Wine, which means that it is possible to run Windows programs under Valgrind with some effort.

This message states our porting rationale. As ever we retain a flexible approach, and are interested in hearing your comments/porting needs if you have any.

Bad, Bad Bug!

Copyright © 2000-2015 Valgrind™ Developers

Hosting kindly donated by Mythic Beasts