From 09d84babc2d1f36bbf9c3aaa624d5aea52461f46 Mon Sep 17 00:00:00 2001
From: Chris Lattner
Date: Sat, 1 Nov 2008 01:46:51 +0000
Subject: [PATCH] minor tweaks.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@58545 91177308-0d34-0410-b5e6-96231b3b80d8
---
www/performance.html | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/www/performance.html b/www/performance.html
index 0c98011726..28ac6a6901 100644
--- a/www/performance.html
+++ b/www/performance.html
@@ -45,7 +45,7 @@ interesting benchmarks:
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 subsystem, the timings have
+order to track the performance of various subsystems, the timings have
been broken down into separate stages where possible:
@@ -55,7 +55,7 @@ been broken down into separate stages where possible:
- -parse-noop: This option runs the parser on the input,
but without semantic analysis or any output. gcc and llvm-gcc have
no equivalent for this option.
- - -fsyntax-only: This option only runs semantic
+
- -fsyntax-only: This option runs the parser with semantic
analysis.
- -emit-llvm -O0: For Clang and llvm-gcc, this option
converts to the LLVM intermediate representation but doesn't
@@ -76,6 +76,10 @@ with -parse-noop (for clang) or -MM with gcc and
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).
+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.
+
--
2.50.1