Add new Splay benchmark to the V8 benchmark suite and remove...

benchmarks/revisions.html

Index: benchmarks/revisions.html
===================================================================
--- benchmarks/revisions.html	(revision 1898)
+++ benchmarks/revisions.html	(working copy)
@@ -20,6 +20,20 @@
 
 </p>
 
+<div class="subtitle"><h3>Version 4 (<a href="http://v8.googlecode.com/svn/data/benchmarks/v4/run.html">link</a>)</h3></div>
+
+<p>The <i>Splay</i> benchmark is a newcomer in version 4.  It
+manipulates a splay tree by adding and removing data nodes, thus
+exercising the memory management subsystem of the JavaScript engine.
+</p>
+
+<p>
+Furthermore, all the unused parts of the Prototype library were
+removed from the RayTrace benchmark. This does not affect the running
+of the benchmark.
+</p>
+
+
 <div class="subtitle"><h3>Version 3 (<a href="http://v8.googlecode.com/svn/data/benchmarks/v3/run.html">link</a>)</h3></div>
 
 <p>Version 3 adds a new benchmark, <i>RegExp</i>.  The RegExp
@@ -32,9 +46,10 @@
 match their input.
 </p>
 
+
 <div class="subtitle"><h3>Version 2 (<a href="http://v8.googlecode.com/svn/data/benchmarks/v2/run.html">link</a>)</h3></div>
 
-<p>For version 2 the crypto benchmark was fixed.  Previously, the
+<p>For version 2 the Crypto benchmark was fixed.  Previously, the
 decryption stage was given plaintext as input, which resulted in an
 error.  Now, the decryption stage is given the output of the
 encryption stage as input.  The result is checked against the original
@@ -49,6 +64,7 @@
 obtaining scores that are the result of an incorrect JavaScript engine
 optimization.</p>
 
+
 <div class="subtitle"><h3>Version 1 (<a href="http://v8.googlecode.com/svn/data/benchmarks/v1/run.html">link</a>)</h3></div>
 
 <p>Initial release.</p>