diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html index 844e6cc5052..c1603be1299 100644 --- a/docs/AliasAnalysis.html +++ b/docs/AliasAnalysis.html @@ -567,7 +567,7 @@ which are intended to allow a pass to keep an AliasAnalysis consistent, however there's no way for a pass to declare in its getAnalysisUsage that it does so. Some passes attempt to use AU.addPreserved<AliasAnalysis>, however this doesn't -actually have any effect. +actually have any effect.

AliasAnalysisCounter (-count-aa) and AliasDebugger (-debug-aa) are implemented as ModulePass classes, so if your diff --git a/docs/BitCodeFormat.html b/docs/BitCodeFormat.html index 8ac444c876a..36d31c9cefb 100644 --- a/docs/BitCodeFormat.html +++ b/docs/BitCodeFormat.html @@ -980,7 +980,7 @@ index in the table of MODULE_CODE_GCNAME entries.

  • unnamed_addr: If present and non-zero, indicates that the function -has unnamed_addr
    • +has unnamed_addr diff --git a/docs/CMake.html b/docs/CMake.html index 002c29d1bc1..fcf2972a728 100644 --- a/docs/CMake.html +++ b/docs/CMake.html @@ -342,7 +342,7 @@
    LLVM_LIT_TOOLS_DIR:STRING
    The path to GnuWin32 tools for tests. Valid on Windows host. Defaults to "", then Lit seeks tools according to %PATH%. - Lit can find tools(eg. grep, sort, &c) on LLVM_LIT_TOOLS_DIR at first, + Lit can find tools(eg. grep, sort, &c) on LLVM_LIT_TOOLS_DIR at first, without specifying GnuWin32 to %PATH%.
    LLVM_ENABLE_FFI:BOOL
    diff --git a/docs/GarbageCollection.html b/docs/GarbageCollection.html index d5fe258ba15..bd114b562fc 100644 --- a/docs/GarbageCollection.html +++ b/docs/GarbageCollection.html @@ -151,14 +151,14 @@ collector models. For instance, the intrinsics permit:

    support a broad class of garbage collected languages including Scheme, ML, Java, C#, Perl, Python, Lua, Ruby, other scripting languages, and more.

    -

    However, LLVM does not itself provide a garbage collector—this should +

    However, LLVM does not itself provide a garbage collector—this should be part of your language's runtime library. LLVM provides a framework for compile time code generation plugins. The role of these plugins is to generate code and data structures which conforms to the binary interface specified by the runtime library. This is similar to the relationship between LLVM and DWARF debugging info, for example. The difference primarily lies in the lack of an established standard in the domain -of garbage collection—thus the plugins.

    +of garbage collection—thus the plugins.

    The aspects of the binary interface with which LLVM's GC support is concerned are:

    diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 7b6759bf870..d6706119708 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -116,7 +116,7 @@ and performance.
  • Read the documentation.
  • Remember that you were warned twice about reading the documentation.
  • Install the llvm-gcc-4.2 front end if you intend to compile C or C++ - (see Install the GCC Front End for details):
    • + (see Install the GCC Front End for details):
    1. cd where-you-want-the-C-front-end-to-live
    2. gunzip --stdout llvm-gcc-4.2-version-platform.tar.gz | tar -xvf -
      3. @@ -344,9 +344,9 @@ up ActivePerl, as these have Windows-specifics that will cause the build to fail.
    3. To use LLVM modules on Win32-based system, - you may configure LLVM with "--enable-shared".
      4. + you may configure LLVM with "--enable-shared".
    4. To compile SPU backend, you need to add - "LDFLAGS=-Wl,--stack,16777216" to configure.
      5. + "LDFLAGS=-Wl,--stack,16777216" to configure.
    @@ -801,11 +801,11 @@ instructions to successfully get and build the LLVM GCC front-end.

    sync automatically with each Subversion commit and contain all necessary git-svn marks (so, you can recreate git-svn metadata locally). Note that right now mirrors reflect only trunk for each project. You can do the - read-only GIT clone of LLVM via: + read-only GIT clone of LLVM via:

    + 
     % git clone http://llvm.org/git/llvm.git
    -

    @@ -1238,7 +1238,7 @@ $ ./hello.bc

    This allows you to execute LLVM bitcode files directly. On Debian, you -can also use this command instead of the 'echo' command above:

    +can also use this command instead of the 'echo' command above:

    diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html index cbc1df430c1..49d10b46d7a 100644 --- a/docs/GettingStartedVS.html +++ b/docs/GettingStartedVS.html @@ -213,14 +213,15 @@

    Note that quite a few of these test will fail.

    -
  • A specific test or test directory can be run with:
    • +
  • A specific test or test directory can be run with: 
     % llvm-lit test/path/to/test
    - +
    • +
    diff --git a/docs/HowToReleaseLLVM.html b/docs/HowToReleaseLLVM.html index 019b5644257..85398d4fca6 100644 --- a/docs/HowToReleaseLLVM.html +++ b/docs/HowToReleaseLLVM.html @@ -82,12 +82,13 @@
      -
    1. Release Administrative Tasks
      2. +
    2. Release Administrative Tasks
      1. Create Release Branch
      2. Update Version Numbers
      -
    3. Building the Release
      4. + +
    4. Building the Release
      1. Build the LLVM Source Distributions
      2. Build LLVM
        3. @@ -95,18 +96,19 @@
      3. Build the Clang Binary Distribution
      4. Target Specific Build Details
      -
    5. Release Qualification Criteria
      6. + +
    6. Release Qualification Criteria
      1. Qualify LLVM
      2. Qualify LLVM-GCC
      3. Qualify Clang
      4. Specific Target Qualification Details
      +
    7. Community Testing
    8. Release Patch Rules
      9. -
    9. Release final tasks
      10. - +
    10. Release final tasks
      1. Update Documentation
      2. Tag the LLVM Final Release
        3. @@ -114,6 +116,7 @@
      3. Update the LLVM Website
      4. Announce the Release
      +
    diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index c67766cbef4..29d10aff03a 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -3,7 +3,6 @@ - LLVM 2.9 Release Notes @@ -119,8 +118,6 @@ look at the language compatibility guide to make sure this is not intentional or a known issue.

    - diff --git a/docs/SourceLevelDebugging.html b/docs/SourceLevelDebugging.html index 2eb9aec8f58..aed42943a33 100644 --- a/docs/SourceLevelDebugging.html +++ b/docs/SourceLevelDebugging.html @@ -804,7 +804,7 @@ DW_TAG_return_variable = 258

    This intrinsic provides information about a local element (ex. variable.) The - first argument is metadata holding alloca for the variable.. The + first argument is metadata holding alloca for the variable. The second argument is metadata containing description of the variable.

    diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html index 051772ec62c..5886c85242c 100644 --- a/docs/TestingGuide.html +++ b/docs/TestingGuide.html @@ -295,6 +295,7 @@ that subdirectory.

    Debugging Information tests
    +

    To run debugging information tests simply checkout the tests inside clang/test directory.

    diff --git a/docs/UsingLibraries.html b/docs/UsingLibraries.html index 5ed8bb34a92..4883db2d939 100644 --- a/docs/UsingLibraries.html +++ b/docs/UsingLibraries.html @@ -26,7 +26,7 @@

    Warning: This document is out of date, for more information please see llvm-config or, - if you use CMake, the CMake LLVM + if you use CMake, the CMake LLVM guide.

    @@ -191,12 +191,12 @@

    This graph shows the dependency of archive libraries on other archive libraries or objects. Where a library has both archive and object forms, only the archive form is shown.

    - Library Dependencies + Library Dependencies

    Dependency Relationships Of Object Files

    This graph shows the dependency of object files on archive libraries or other objects. Where a library has both object and archive forms, only the dependency to the archive form is shown.

    - Object File Dependencies + Object File Dependencies

    The following list shows the dependency relationships between libraries in textual form. The information is the same as shown on the graphs but arranged alphabetically.

    @@ -280,8 +280,8 @@
  • libLLVMSystem.a
  • libLLVMbzip2.a
    • -
    libLLVMSystem.a
      -
    +
    libLLVMSystem.a
    +
    libLLVMTarget.a
    • libLLVMCore.a
    • libLLVMSupport.a
      • @@ -295,8 +295,8 @@
    • libLLVMTarget.a
    • libLLVMipa.a
    -
    libLLVMbzip2.a
      -
    +
    libLLVMbzip2.a
    +
    libLLVMipa.a
    • libLLVMAnalysis.a
    • libLLVMCore.a
      • @@ -430,7 +430,7 @@
      Valid CSS + src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"> Valid HTML 4.01 Reid Spencer diff --git a/docs/WritingAnLLVMPass.html b/docs/WritingAnLLVMPass.html index 866f406eff4..6d18d192e31 100644 --- a/docs/WritingAnLLVMPass.html +++ b/docs/WritingAnLLVMPass.html @@ -185,7 +185,7 @@ source tree in the lib/Transforms/Hello directory.

      lib/Transforms/Hello. Finally, you must set up a build script (Makefile) that will compile the source code for the new pass. To do this, copy the following into Makefile:

      -
      + 
       # Makefile for hello pass
@@ -301,7 +301,7 @@ function.
      
 initialization value is not important.
      
 
 
      -  static RegisterPass X("hello", "Hello World Pass",
+  static RegisterPass<Hello> X("hello", "Hello World Pass",
                         false /* Only looks at CFG */,
                         false /* Analysis Pass */);
 }  // end of anonymous namespace
@@ -337,7 +337,7 @@ is supplied as fourth argument. 
      
   };
   
   char Hello::ID = 0;
-  static RegisterPass X("hello", "Hello World Pass", false, false);
+  static RegisterPass<Hello> X("hello", "Hello World Pass", false, false);
 }
 
 
      
diff --git a/docs/tutorial/LangImpl4.html b/docs/tutorial/LangImpl4.html
index 99bc16b823f..2d876229c41 100644
--- a/docs/tutorial/LangImpl4.html
+++ b/docs/tutorial/LangImpl4.html
@@ -1078,7 +1078,7 @@ int main() {
 
   // Create the JIT.  This takes ownership of the module.
   std::string ErrStr;
-  TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
+TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
   if (!TheExecutionEngine) {
     fprintf(stderr, "Could not create ExecutionEngine: %s\n", ErrStr.c_str());
     exit(1);
diff --git a/docs/tutorial/LangImpl5.html b/docs/tutorial/LangImpl5.html
index 33837175e93..2c1a07f6144 100644
--- a/docs/tutorial/LangImpl5.html
+++ b/docs/tutorial/LangImpl5.html
@@ -1721,7 +1721,7 @@ int main() {
 
   // Create the JIT.  This takes ownership of the module.
   std::string ErrStr;
-  TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
+  TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
   if (!TheExecutionEngine) {
     fprintf(stderr, "Could not create ExecutionEngine: %s\n", ErrStr.c_str());
     exit(1);
diff --git a/docs/tutorial/LangImpl6.html b/docs/tutorial/LangImpl6.html
index a270fe1efa5..72fa9c3b080 100644
--- a/docs/tutorial/LangImpl6.html
+++ b/docs/tutorial/LangImpl6.html
@@ -1758,7 +1758,7 @@ int main() {
 
   // Create the JIT.  This takes ownership of the module.
   std::string ErrStr;
-  TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
+  TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
   if (!TheExecutionEngine) {
     fprintf(stderr, "Could not create ExecutionEngine: %s\n", ErrStr.c_str());
     exit(1);