From: Chris Lattner Date: Sun, 20 Jul 2008 04:22:06 +0000 (+0000) Subject: Add a space, ted apparently has philosophical problems with spaces ;-) X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d9069d1cbb28b4aa76cd0b0f7879885470429612;p=clang Add a space, ted apparently has philosophical problems with spaces ;-) git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@53808 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/www/StaticAnalysisUsage.html b/www/StaticAnalysisUsage.html index d050012f73..2d97a9b9b3 100644 --- a/www/StaticAnalysisUsage.html +++ b/www/StaticAnalysisUsage.html @@ -92,7 +92,7 @@ during a project build.

In the first case scan-build analyzes the code of a project built -with make, andin the second case scan-build analyzes a project +with make, and in the second case scan-build analyzes a project built using xcodebuild. In general, the format is:

@@ -100,7 +100,7 @@ built using xcodebuild. In general, the format is: 

Operationally, scan-build literally runs with all of the -subsequent options passed to it. For example

+subsequent options passed to it. For example:

    $ scan-build make -j4
@@ -225,7 +225,7 @@ what it's doing; two -v options emit more information. Redirecting the
 output of scan-build to a text file (make sure to redirect standard
 error) is useful for filing bug reports against scan-build or the
 analyzer, as we can see the exact options (and files) passed to the analyzer.
-For more comprehendible logs, don't perform a parallel build.

+For more comprehensible logs, don't perform a parallel build.

Debugging the Analyzer