|
From: <sv...@va...> - 2005-09-13 20:26:02
|
Author: njn Date: 2005-09-13 21:25:57 +0100 (Tue, 13 Sep 2005) New Revision: 193 Log: Rework ports page to talk about platforms, rather than separating arch an= d OS. Modified: trunk/devel/platforms.html trunk/info/news.html Modified: trunk/devel/platforms.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/devel/platforms.html 2005-09-12 20:55:43 UTC (rev 192) +++ trunk/devel/platforms.html 2005-09-13 20:25:57 UTC (rev 193) @@ -1,68 +1,60 @@ <h1>Supported Platforms</h1> =20 -<p>We are working to make future Valgrinds (3.0 and above) more +<p>We are working to make future Valgrinds (3.0.0 and above) more portable.</p> =20 <div class=3D"hr_brown"><hr/></div> =20 -<a name=3D"arch_ports"></a><h2>Architectures</h2> +<a name=3D"curr_mainline"></a><h2>Current Mainline</h2> =20 -<dl class=3D"spaced"> +<p>The Valgrind 3.0.X series supports the following platforms.</p> +<ul> +<li><b>x86/Linux:</b> support is mature and almost complete. +<li><b>AMD64/Linux:</b> support is new but fairly complete. +<li><b>PPC32/Linux:</b> support is new, incomplete, but improving. +</ul> =20 -<dt><b>x86</b></dt> -<dd>The stable 2.4.0 release only supports=20 - Linux running on x86 machines.</dd> +<p>You must be running Linux kernel 2.4.X, 2.5.X or 2.6.X, and glibc 2.2= .X, +2.3.X or 2.4.X. That covers the vast majority of installed systems at +present.</p> =20 -<dt><b>AMD64</b></dt> -<dd>valgrind-3.0 supports AMD64 on Linux.</dd> +<p>For details of which distributions the current release +(<?php echo $config['release-version']; ?>) builds and runs its +regression tests on, see the=20 +<a href=3D"/downloads/source_code.html#current">release notes</a>.</p> =20 =20 -<dt><b>PowerPC/Linux</b></dt> -<dd>Paul Mackerras has an experimental port of valgrind to - PowerPC/Linux which you can - <a href=3D"http://ozlabs.org/~paulus/">download - here</a>. Caveat emptor applies! -</dd> +<a name=3D"old_mainline"></a><h2>Old Mainline</h2> =20 -<dd>In the Valgrind-3.0 series, support for 32-bit PowerPC on Linux is -under development.</dd> +<p>All Valgrind versions prior to 3.0.0 supported only <b>x86/Linux</b>.= </p> =20 =20 -</dl> +<a name=3D"experimental"></a><h2>Experimental</h2> =20 +<p>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.</p> =20 +<ul> +<li><p><b>x86/FreeBSD:</b> Doug Rabson and others haved done a fairly=20 + complete port of Valgrind 2.X. Snapshots of the work in progress ar= e at + <a href=3D"http://www.freebsd.org/cgi/ports.cgi?query=3Dvalgrind">th= is + FreeBSD page</a></p></li>. =20 -<div class=3D"hr_brown"><hr/></div> +<li><p><b>PPC32/Linux:</b> Paul Mackerras has an experimental port of + Valgrind 2.X which you can + <a href=3D"http://ozlabs.org/~paulus/">download here</a>.=20 + This was the basis of the PPC32/Linux port included in Valgrind 3.0.= 0 + and above.</p></li> =20 -<a name=3D"os_ports"></a><h2>Operating Systems</h2> +<li><p><b>x86/NetBSD:</b> Eric Auge, Kailash Sethuraman and Peter Bex + are doing a port of Valgrind 3.X, available at=20 + <a href=3D"http://http://vg4nbsd.berlios.de/">this page</a>.=20 + </p></li> +</ul> =20 -<dl class=3D"spaced"> =20 -<dt><b>*/Linux</b></dt> =20 - <dd>You must be running Linux kernel 2.4.X, 2.5.X or 2.6.X, and - glibc 2.2.X, 2.3.X or 2.4.X. That covers the vast majority of - installed systems at present. - - <p>For details of which distributions the current release - (<?php echo $config['release-version']; ?>) builds - and runs its regression tests on, see the=20 - <a href=3D"/downloads/source_code.html#current">release - notes</a>.</p> - </dd> - - -<dt><b>FreeBSD</b></dt> - - <dd>Doug Rabson and others haved done a fairly complete port for x86. - Snapshots of the work in progress are at <a - href=3D"http://www.freebsd.org/cgi/ports.cgi?query=3Dvalgrind">this F= reeBSD - page</a>. We hope to integrate this support into Valgrind at some - point.</dd> - -</dl> - - <div class=3D"hr_brown"><hr/></div> =20 <a name=3D"porting_plans"></a><h2>Porting Plans</h2> @@ -74,7 +66,7 @@ =20 <p>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 +it does. Also, each platform port has CPU-specific code, OS-specific code and platform-specific code, and testing all the combinations is difficult.</p> =20 @@ -84,7 +76,7 @@ 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 forseeable future. The following +supported properly, at least in the foreseeable future. The following table summarises our current porting priorities.</p> =20 <table class=3D"form" width=3D"100%" cellspacing=3D"0" cellpadding=3D"3"= border=3D"1"> @@ -97,12 +89,14 @@ </table> =20 <p>There are experimental ppc32/darwin and x86/FreeBSD ports for Valgrin= d 2.X. -They could be made to work with 3.x with some effort. A (much less matu= re) -port for x86/Solaris is also being worked on.</p> +They could be made to work with 3.X with some effort. Less mature +ports for x86/Solaris and x86/NetBSD are also being worked on.</p> =20 -<p>ppc32/darwin is a high priority; it would be great to have Valgrind = running -on Apple machines. Once x86/darwin machines become available, that too -will become a high priority. amd64/darwin will presumably eventually be= come +<p>ppc32/darwin is a high priority; it would be great to have Valgrind +running on Apple machines, as it would make Valgrind usable with a lot o= f +new software (e.g. Microsoft Office for Mac!), more so than x86/BSD port= s, +for example. Once x86/darwin machines become available, that too will +become a high priority. amd64/darwin will presumably eventually become important. 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.</p> Modified: trunk/info/news.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/news.html 2005-09-12 20:55:43 UTC (rev 192) +++ trunk/info/news.html 2005-09-13 20:25:57 UTC (rev 193) @@ -52,7 +52,7 @@ is available.</li> =20 <li>March 04 2004:<br /> An experimental=20 - <a href=3D"/devel/platforms.html#arch_ports">PowerPC port</a>=20 + <a href=3D"/devel/platforms.html">PowerPC port</a>=20 is available.</li> =20 <li>February 15 2004:<br /> Valgrind CVS now includes=20 |