|
From: <sv...@va...> - 2014-08-19 18:47:45
|
Author: florian
Date: Tue Aug 19 18:47:35 2014
New Revision: 488
Log:
Update porting priorities. Remove outdated information.
Modified:
trunk/info/platforms.html
Modified: trunk/info/platforms.html
==============================================================================
--- trunk/info/platforms.html (original)
+++ trunk/info/platforms.html Tue Aug 19 18:47:35 2014
@@ -77,30 +77,9 @@
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.</p>
+supported properly, at least in the foreseeable future.</p>
-<table class="form" width="100%" cellspacing="0" cellpadding="3" border="1">
-<tr><th> </th> <th>Linux </th> <th>Darwin</th> <th>*BSD</th> <th>Solaris</th></tr>
-<tr><td>x86 </td> <td>done </td> <td>done </td> <td>low </td> <td> </td></tr>
-<tr><td>amd64</td> <td>done </td> <td>done </td> <td>low </td> <td> </td></tr>
-<tr><td>ppc32</td> <td>done </td> <td> </td> <td> </td> <td> </td></tr>
-<tr><td>ppc64</td> <td>done </td> <td> </td> <td> </td> <td> </td></tr>
-<tr><td>s390x</td> <td>done </td> <td> </td> <td> </td> <td> </td></tr>
-<tr><td>arm </td> <td>medium</td> <td> </td> <td> </td> <td> </td></tr>
-<tr><td>mips </td> <td>in progress </td> <td> </td> <td> </td> <td> </td></tr>
-</table>
-
-<p>Some experimental ports have been worked on, as mentioned above. A less
-mature port for x86/Solaris has also been worked on.</p>
-
-<p>Of the other table entries Arm/Linux is the most interesting.
-MIPS/Linux, x86/BSD, amd64/BSD and x86/Solaris are
-lower priorities.</p>
-
-<p>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
+<p>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
@@ -108,10 +87,6 @@
Valgrind is quite usable in conjunction with Wine, which means that it is
possible to run Windows programs under Valgrind with some effort.</p>
-<p>This message states our porting rationale and current priorities.
+<p>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.</p>
-
-<p>November 24, 2011.</p>
-
-
|