[cfe-commits] r58634 - /cfe/trunk/www/performance.html

[Daniel Dunbar]

Author: ddunbar
Date: Mon Nov  3 14:03:58 2008
New Revision: 58634

URL: http://llvm.org/viewvc/llvm-project?rev=58634&view=rev
Log:
Clarify performance experiments description based on feedback from
Eric C, thanks!

Modified:
    cfe/trunk/www/performance.html

Modified: cfe/trunk/www/performance.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/performance.html?rev=58634&r1=58633&r2=58634&view=diff

==============================================================================
--- cfe/trunk/www/performance.html (original)
+++ cfe/trunk/www/performance.html Mon Nov  3 14:03:58 2008
@@ -45,7 +45,7 @@
 
 <p>Measurements are done by serially processing each file in the
 respective benchmark, using Clang, gcc, and llvm-gcc as compilers. In
-order to track the performance of various subsystems, the timings have
+order to track the performance of various subsystems the timings have
 been broken down into separate stages where possible:
 
 <ul>
@@ -76,6 +76,12 @@
 llvm-gcc. This amounts to a fairly accurate measure of only the time
 to perform semantic analysis (and parsing, in the case of gcc and llvm-gcc).</p>
 
+<p>These timings are chosen to break down the compilation process for
+clang as much as possible. The graphs below show these numbers
+combined so that it is easy to see how the time for a particular task
+is divided among various components. For example, <tt>-S -O0</tt>
+includes the time of <tt>-fsyntax-only</tt> and <tt>-emit-llvm -O0</tt>.</p>
+
 <p>Note that we already know that the LLVM optimizers are substantially (30-40%)
 faster than the GCC optimizers at a given -O level, so we only focus on -O0
 compile time here.</p>