Supported Platforms

Current Mainline

The Valgrind 3.4.X series supports the following platforms.

• x86/Linux: support is mature and almost complete.
• AMD64/Linux: support is mature and almost complete.
• PPC32/Linux: support is new but fairly complete.
• PPC64/Linux: support is new but fairly complete.

(Note that AMD64 is just another name for x86-64, and that Valgrind works fine on Intel machines.) On Linux, you must be running kernel 2.4.X or later, and glibc 2.2.X or later. That covers the vast majority of installed systems at present.

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

Old Mainline

All Valgrind versions prior to 3.0.0 supported only x86/Linux.

Under Development

The current SVN trunk also supports the following platforms.

• x86/MacOSX: support is new and somewhat complete.
• AMD64/MacOSX: support is new and less complete.

(Note that the core of Mac OS X is called "Darwin", and so these platforms are often called x86/Darwin and AMD64/Darwin.) You must be running Mac OS 10.5.X or greater.

Experimental

The following experimental ports have been done. Note that they have varying levels of completeness and 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 2.X. 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.

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. The following table summarises our current porting priorities.

	Linux	*BSD	Darwin	Solaris
x86	done	low	done (unreleased)	low
amd64	done	low	done (unreleased)
ppc32	done
ppc64	done
arm	low
mips	low

Some experimental ports have been worked on, as mentioned above. A less mature port for x86/Solaris has also been worked on.

Of the other table entries Arm/Linux or MIPS/Linux might be useful for embedded developers. x86/BSD, amd64/BSD and x86/Solaris are lower priorities.

There are many platforms not mentioned here. Some are of little interest (eg. SPARC/*, */AIX). Some would be technically difficult (eg. IA64/*). In particular Windows is not under consideration here because porting to it would require so many changes it would almost be a separate project. 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 and current priorities. As ever we retain a flexible approach, and are interested in hearing your comments/porting needs if you have any.

May 29, 2009.