[llvm-commits] [zorg] r152572 - /zorg/trunk/lnt/lnt/tests/compile.py

[Daniel Dunbar]

Author: ddunbar
Date: Mon Mar 12 15:56:33 2012
New Revision: 152572

URL: http://llvm.org/viewvc/llvm-project?rev=152572&view=rev
Log:
[LNT] lnt.tests.compile: Fix up help text a bit.

Modified:
    zorg/trunk/lnt/lnt/tests/compile.py

Modified: zorg/trunk/lnt/lnt/tests/compile.py
URL: http://llvm.org/viewvc/llvm-project/zorg/trunk/lnt/lnt/tests/compile.py?rev=152572&r1=152571&r2=152572&view=diff
==============================================================================
--- zorg/trunk/lnt/lnt/tests/compile.py (original)
+++ zorg/trunk/lnt/lnt/tests/compile.py Mon Mar 12 15:56:33 2012
@@ -455,9 +455,6 @@
 usage_info = """
 Script for testing compile time performance.
 
-Currently this is primarily intended to test the raw compiler performance (not
-its scalability or its performance in parallel builds).
-
 This tests:
  - PCH Generation for Cocoa.h
    o File Size
@@ -472,7 +469,7 @@
    o Memory Usage
    o Time
  - Full Build Times
-   o Total Build Time (serialized) (using xcodebuild)
+   o Total Build Time (using xcodebuild)
 
 TODO:
  - Objective-C Compile Time, with PCH
@@ -495,13 +492,8 @@
  - fsyntax-only (lex/parse/sema time)
  - emit-llvm-only (IRgen time)
  - emit-llvm (.bc output time and size, mostly to track output file size)
- - S (codegen time and size)
+ - emit-codegen-only (codegen time, without assembler)
  - c (assembly time and size)
-
-FIXME: In the past, we have generated breakdown timings of full builds using
-Make or xcodebuild by interposing scripts to stub out parts of the compilation
-process. This is fragile, but can also be very useful when trying to understand
-where the time is going in a full build.
 """
 
 class CompileTest(builtintest.BuiltinTest):