diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html index 25a27f36e46..63567876e37 100644 --- a/docs/AliasAnalysis.html +++ b/docs/AliasAnalysis.html @@ -75,7 +75,7 @@ indicating that two pointers always point to the same object, might point to the same object, or are known to never point to the same object.

The LLVM AliasAnalysis +href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis class is the primary interface used by clients and implementations of alias analyses in the LLVM system. This class is the common interface between clients of alias analysis information and the implementations providing it, and is @@ -102,7 +102,7 @@ know.

The AliasAnalysis +href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis class defines the interface that the various alias analysis implementations should support. This class exports two important enums: AliasResult and ModRefResult which represent the result of an alias query or a @@ -951,7 +951,7 @@ algorithm will have a lower number of may aliases).

src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"> Chris Lattner
- LLVM Compiler Infrastructure
+ LLVM Compiler Infrastructure
Last modified: $Date$ diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html index 81dce4f42a5..e2a3611db27 100644 --- a/docs/Bugpoint.html +++ b/docs/Bugpoint.html @@ -230,7 +230,7 @@ non-obvious ways. Here are some hints and tips:

src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"> Chris Lattner
- LLVM Compiler Infrastructure
+ LLVM Compiler Infrastructure
Last modified: $Date$ diff --git a/docs/BytecodeFormat.html b/docs/BytecodeFormat.html index be231781680..8f7ec511d61 100644 --- a/docs/BytecodeFormat.html +++ b/docs/BytecodeFormat.html @@ -747,7 +747,7 @@ describes the latest version, 1.3):

Note that we plan to eventually expand the target description capabilities -of bytecode files to target +of bytecode files to target triples.

@@ -1553,7 +1553,7 @@ possible.

Instructions encode an opcode that identifies the kind of instruction. Opcodes are an enumerated integer value. The specific values used depend on the version of LLVM you're using. The opcode values are defined in the - + include/llvm/Instruction.def file. You should check there for the most recent definitions. The table below provides the opcodes defined as of the writing of this document. The table associates each opcode mnemonic with @@ -2147,7 +2147,7 @@ From 1.1 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"> Reid Spencer and Chris Lattner
-The LLVM Compiler Infrastructure
+The LLVM Compiler Infrastructure
Last modified: $Date$ diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index a7797c6b633..c354213687c 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -184,7 +184,7 @@ SPARC V9 code. It is highly recommended that you use the V8 ABI with LLVM, as shown below. Also, note that Solaris has trouble with various wide (multibyte) character functions from C as referenced from C++, so we typically configure with ---disable-c-mbchar (cf. Bug 206). +--disable-c-mbchar (cf. Bug 206). 

@@ -312,7 +312,7 @@ Developed by:
 
     University of Illinois at Urbana-Champaign
 
-    http://llvm.cs.uiuc.edu
+    http://llvm.org
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
@@ -356,7 +356,7 @@ purpose.  It is provided "as is" without express or implied warranty.
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!">
 
   Brian Gaeke

-  LLVM Compiler Infrastructure

+  LLVM Compiler Infrastructure

   Last modified: $Date$
 
 
diff --git a/docs/CodeGenerator.html b/docs/CodeGenerator.html
index 406d77cbef4..ebe5fd9cc59 100644
--- a/docs/CodeGenerator.html
+++ b/docs/CodeGenerator.html
@@ -1296,7 +1296,7 @@ a character per operand with an optional special size. For example:

   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" />
 
   Chris Lattner

-  The LLVM Compiler Infrastructure

+  The LLVM Compiler Infrastructure

   Last modified: $Date$
 
 
diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 84b9adb66a1..df6eb90b9be 100644
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -653,7 +653,7 @@ something.

   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!">
 
   Chris Lattner

-  LLVM Compiler Infrastructure

+  LLVM Compiler Infrastructure

   Last modified: $Date$
 
 
diff --git a/docs/CommandLine.html b/docs/CommandLine.html
index 89363f95e5b..7da06e8ddbf 100644
--- a/docs/CommandLine.html
+++ b/docs/CommandLine.html
@@ -1899,7 +1899,7 @@ tutorial.

   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!">
 
   Chris Lattner

-  LLVM Compiler Infrastructure

+  LLVM Compiler Infrastructure

   Last modified: $Date$
 
 
diff --git a/docs/CompilerDriver.html b/docs/CompilerDriver.html
index 5568b20895f..c73723efd08 100644
--- a/docs/CompilerDriver.html
+++ b/docs/CompilerDriver.html
@@ -814,7 +814,7 @@ optimization.

  href="http://validator.w3.org/check/referer">Valid HTML 4.01!Reid Spencer

-The LLVM Compiler Infrastructure

+The LLVM Compiler Infrastructure

 Last modified: $Date$
 
 
 
Bug 351

 

-  
See bug 351
+  
See bug 351
   for further details on the progress of this work

 

 
@@ -337,7 +337,7 @@
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!">
 
   Reid Spencer

-  LLVM Compiler Infrastructure

+  LLVM Compiler Infrastructure

   Last modified: $Date$
 
 
diff --git a/docs/TableGenFundamentals.html b/docs/TableGenFundamentals.html
index daa06db1c0b..7924bd9a247 100644
--- a/docs/TableGenFundamentals.html
+++ b/docs/TableGenFundamentals.html
@@ -559,7 +559,7 @@ should highlight the APIs in TableGen/Record.h.

   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" />
 
   Chris Lattner

-  LLVM Compiler Infrastructure

+  LLVM Compiler Infrastructure

   Last modified: $Date$
 
 
diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html
index d2c3bd06637..2f88ada2ce3 100644
--- a/docs/TestingGuide.html
+++ b/docs/TestingGuide.html
@@ -416,7 +416,7 @@ directory to run them.

 
    
   
  1. cd into the llvm/projects directory
    2. 
   
  2. check out the llvm-test module with:
    
-  cvs -d :pserver:anon@llvm.cs.uiuc.edu:/var/cvs/llvm co -PR llvm-test
     
+  cvs -d :pserver:anon@llvm.org:/var/cvs/llvm co -PR llvm-test
     
   This will get the test suite into llvm/projects/llvm-test
    3. 
   
  3. configure the test suite. You can do this one of two ways:
   
      
@@ -468,7 +468,7 @@ will help you separate benign warnings from actual test failures.
      
 
      
 
 
      
-The LLVM Nightly Testers
+The LLVM Nightly Testers
 automatically check out an LLVM tree, build it, run the "nightly" 
 program test (described above), run  all of the feature and regression tests, 
 and then delete the checked out tree.  This tester is designed to ensure that 
@@ -492,7 +492,7 @@ The optimized x86 Linux nightly test is run from just such a script:
      
 
       #!/bin/bash
 BASE=/proj/work/llvm/nightlytest
-export CVSROOT=:pserver:anon@llvm.cs.uiuc.edu:/var/cvs/llvm
+export CVSROOT=:pserver:anon@llvm.org:/var/cvs/llvm
 export BUILDDIR=$BASE/build 
 export WEBDIR=$BASE/testresults 
 export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
@@ -521,7 +521,7 @@ we'll link your page to the global tester page.  Thanks!
      
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" />
 
   John T. Criswell, Reid Spencer, and Tanya Lattner
      
-  The LLVM Compiler Infrastructure
      
+  The LLVM Compiler Infrastructure
      
   Last modified: $Date$
 
 
diff --git a/docs/UsingLibraries.html b/docs/UsingLibraries.html
index fd134bd7664..a9b6b07f5fd 100644
--- a/docs/UsingLibraries.html
+++ b/docs/UsingLibraries.html
@@ -496,7 +496,7 @@
     src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" />
   Reid Spencer
 
-The LLVM Compiler Infrastructure 
+The LLVM Compiler Infrastructure 
 
      Last modified: $Date$ 
      
 
 
diff --git a/docs/WritingAnLLVMBackend.html b/docs/WritingAnLLVMBackend.html
index ea5cd9c3da5..c487bc63571 100644
--- a/docs/WritingAnLLVMBackend.html
+++ b/docs/WritingAnLLVMBackend.html
@@ -250,7 +250,7 @@ how the C backend is written.
      
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" />
 
   Misha Brukman
      
-  The LLVM Compiler Infrastructure
+  The LLVM Compiler Infrastructure
   
      
   Last modified: $Date$
 
diff --git a/docs/WritingAnLLVMPass.html b/docs/WritingAnLLVMPass.html
index 46c07d6bad5..0ca54994f51 100644
--- a/docs/WritingAnLLVMPass.html
+++ b/docs/WritingAnLLVMPass.html
@@ -115,7 +115,7 @@ build the analysis results that are used by these transformations, and they are,
 above all, a structuring technique for compiler code.
      
 
 
      All LLVM passes are subclasses of the Pass
+href="http://llvm.org/doxygen/classllvm_1_1Pass.html">Pass
 class, which implement functionality by overriding virtual methods inherited
 from Pass.  Depending on how your pass works, you should inherit from
 the ModulePass, 
 Start out with:
      
 
 
      -#include "llvm/Pass.h"
-#include "llvm/Function.h"
+#include "llvm/Pass.h"
+#include "llvm/Function.h"
 
      
 
 
      Which are needed because we are writing a Pass, and
+href="http://llvm.org/doxygen/classllvm_1_1Pass.html">Pass, and
 we are operating on Function's.
      
+href="http://llvm.org/doxygen/classllvm_1_1Function.html">Function's.
      
 
 
      Next we have:
      
 
      @@ -242,7 +242,7 @@ information.
      
 
      
 
 
      This declares a "Hello" class that is a subclass of FunctionPass.
+href="http://llvm.org/doxygen/classllvm_1_1FunctionPass.html">FunctionPass.
 The different builtin pass subclasses are described in detail later, but for now, know that FunctionPass's operate a function at a
@@ -276,8 +276,8 @@ depending on what it is to be used for.  For "optimizations" we use the
 
      As a whole, the .cpp file looks like:
      
 
 
      -#include "llvm/Pass.h"
-#include "llvm/Function.h"
+#include "llvm/Pass.h"
+#include "llvm/Function.h"
 
 using namespace llvm;
 
@@ -424,7 +424,7 @@ slow.
      
 
      
 
 
      The most plain and boring type of pass is the "ImmutablePass"
+href="http://llvm.org/doxygen/classllvm_1_1ImmutablePass.html">ImmutablePass"
 class.  This pass type is used for passes that do not have to be run, do not
 change state, and never need to be updated.  This is not a normal type of
 transformation or analysis, but can provide information about the current
@@ -447,7 +447,7 @@ invalidated, and are never "run".
      
 
      
 
 
      The "ModulePass"
+href="http://llvm.org/doxygen/classllvm_1_1ModulePass.html">ModulePass"
 class is the most general of all superclasses that you can use.  Deriving from
 ModulePass indicates that your pass uses the entire program as a unit,
 refering to function bodies in no predictable order, or adding and removing
@@ -485,7 +485,7 @@ false otherwise.
      
 
      
 
 
      The "CallGraphSCCPass"
+href="http://llvm.org/doxygen/classllvm_1_1CallGraphSCCPass.html">CallGraphSCCPass"
 is used by passes that need to traverse the program bottom-up on the call graph
 (callees before callers).  Deriving from CallGraphSCCPass provides some
 mechanics for building and traversing the CallGraph, but also allows the system
@@ -593,7 +593,7 @@ program being compiled.
      
 
      
 
 
      In contrast to ModulePass subclasses, FunctionPass
+href="http://llvm.org/doxygen/classllvm_1_1Pass.html">FunctionPass
 subclasses do have a predictable, local behavior that can be expected by the
 system.  All FunctionPass execute on each function in the program
 independent of all of the other functions in the program.
@@ -638,7 +638,7 @@ scheduled to overlap with any other pass executions (thus it should be very
 fast).
      
 
 
      A good example of how this method should be used is the LowerAllocations
+href="http://llvm.org/doxygen/LowerAllocations_8cpp-source.html">LowerAllocations
 pass.  This pass converts malloc and free instructions into
 platform dependent malloc() and free() function calls.  It
 uses the doInitialization method to get a reference to the malloc and
@@ -853,7 +853,7 @@ registering a pass that logically should be available for use in the
 Register* templates that should be used if you want your pass listed by
 multiple or no utilities.  This template takes an extra third argument that
 specifies which tools it should be listed in.  See the PassSupport.h
+href="http://llvm.org/doxygen/PassSupport_8h-source.html">PassSupport.h
 file for more information.
 
 
@@ -934,7 +934,7 @@ having any prerequisite passes, and invalidating all other passes.
      
 
      By implementing the getAnalysisUsage method, the required and
 invalidated sets may be specified for your transformation.  The implementation
 should fill in the AnalysisUsage
+href="http://llvm.org/doxygen/classllvm_1_1AnalysisUsage.html">AnalysisUsage
 object with information about which passes are required and not invalidated.  To
 do this, a pass may call any of the following methods on the AnalysisUsage
 object:
      
@@ -1011,9 +1011,9 @@ the fact that it hacks on the CFG.
 
         // This is an example implementation from an analysis, which does not modify
   // the program at all, yet has a prerequisite.
-  void PostDominanceFrontier::getAnalysisUsage(AnalysisUsage &AU) const {
+  void PostDominanceFrontier::getAnalysisUsage(AnalysisUsage &AU) const {
     AU.setPreservesAll();
-    AU.addRequired<PostDominatorTree>();
+    AU.addRequired<PostDominatorTree>();
   }
 
      
 
@@ -1021,9 +1021,9 @@ the fact that it hacks on the CFG.
 
 
         // This example modifies the program, but does not modify the CFG
-  void LICM::getAnalysisUsage(AnalysisUsage &AU) const {
+  void LICM::getAnalysisUsage(AnalysisUsage &AU) const {
     AU.setPreservesCFG();
-    AU.addRequired<LoopInfo>();
+    AU.addRequired<LoopInfo>();
   }
 
      
 
@@ -1128,16 +1128,16 @@ implementation pool.  Also, a default implementation of the interface
 href="#registerag">RegisterAnalysisGroup.
      
 
 
      As a concrete example of an Analysis Group in action, consider the AliasAnalysis
+href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis
 analysis group.  The default implementation of the alias analysis interface (the
 basicaa
+href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">basicaa
 pass) just does a few simple checks that don't require significant analysis to
 compute (such as: two different globals can never alias each other, etc).
 Passes that use the AliasAnalysis
+href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis
 interface (for example the gcse pass), do
+href="http://llvm.org/doxygen/structGCSE.html">gcse pass), do
 not care which implementation of alias analysis is actually provided, they just
 use the designated interface.
      
 
@@ -1164,7 +1164,7 @@ Unlike registration of passes, there is no command line argument to be specified
 for the Analysis Group Interface itself, because it is "abstract":
      
 
 
      -  static RegisterAnalysisGroup<AliasAnalysis> A("Alias Analysis");
+  static RegisterAnalysisGroup<AliasAnalysis> A("Alias Analysis");
 
      
 
 
      Once the analysis is registered, passes can declare that they are valid
@@ -1177,13 +1177,13 @@ implementations of the interface by using the following code:
      
   B("somefancyaa", "A more complex alias analysis implementation");
 
   // Declare that we implement the AliasAnalysis interface
-  RegisterAnalysisGroup<AliasAnalysis, FancyAA> C;
+  RegisterAnalysisGroup<AliasAnalysis, FancyAA> C;
 }
 
      
 
 
      This just shows a class FancyAA that is registered normally, then
 uses the RegisterAnalysisGroup template to "join" the AliasAnalysis
+href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis
 analysis group.  Every implementation of an analysis group should join using
 this template.  A single pass may join multiple different analysis groups with
 no problem.
      
@@ -1191,11 +1191,11 @@ no problem.
      
 
       namespace {
   // Analysis Group implementations must be registered normally...
-  RegisterOpt<BasicAliasAnalysis>
+  RegisterOpt<BasicAliasAnalysis>
   D("basicaa", "Basic Alias Analysis (default AA impl)");
 
   // Declare that we implement the AliasAnalysis interface
-  RegisterAnalysisGroup<AliasAnalysis, BasicAliasAnalysis, true> E;
+  RegisterAnalysisGroup<AliasAnalysis, BasicAliasAnalysis, true> E;
 }
 
      
 
@@ -1203,7 +1203,7 @@ no problem.
      
 argument to the RegisterAnalysisGroup template).  There must be exactly
 one default implementation available at all times for an Analysis Group to be
 used.  Here we declare that the BasicAliasAnalysis
+href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">BasicAliasAnalysis
 pass is the default implementation for the interface.
      
 
 
@@ -1216,7 +1216,7 @@ pass is the default implementation for the interface.
      
 
 
      
 
      The Statistic
+href="http://llvm.org/doxygen/Statistic_8h-source.html">Statistic
 class is designed to be an easy way to expose various success
 metrics from passes.  These statistics are printed at the end of a
 run, when the -stats command line option is enabled on the command
@@ -1234,9 +1234,9 @@ line. See the St
 
      
 
 
      The PassManager
+href="http://llvm.org/doxygen/PassManager_8h-source.html">PassManager
 class
+href="http://llvm.org/doxygen/classllvm_1_1PassManager.html">class
 takes a list of passes, ensures their prerequisites
 are set up correctly, and then schedules passes to run efficiently.  All of the
 LLVM tools that run passes use the PassManager for execution of these
@@ -1267,7 +1267,7 @@ etc... until the entire program has been run through the passes.
 the LLVM program representation for a single function at a time, instead of
 traversing the entire program.  It reduces the memory consumption of compiler,
 because, for example, only one DominatorSet
+href="http://llvm.org/doxygen/classllvm_1_1DominatorSet.html">DominatorSet
 needs to be calculated at a time.  This also makes it possible some interesting enhancements in the future.
      
 
@@ -1592,7 +1592,7 @@ href="#ModulePass">ModulePass, only the other way around.
      
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" />
 
   Chris Lattner
      
-  The LLVM Compiler Infrastructure
      
+  The LLVM Compiler Infrastructure
      
   Last modified: $Date$
 
 
diff --git a/docs/index.html b/docs/index.html
index 2e8f6432529..a390dc705f1 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -20,7 +20,7 @@
 
 
   
      
-      
+      
       
      
       
   
      
@@ -28,7 +28,7 @@
 
      
 
 
          
-  
      Written by The LLVM Team
      
+  
      Written by The LLVM Team
      
 
      
 
 
@@ -36,7 +36,7 @@
 
 
 
@@ -249,7 +249,7 @@ times each day, making it a high volume list.
   Valid HTML 4.01!
 
-  LLVM Compiler Infrastructure
      
+  LLVM Compiler Infrastructure
      
   Last modified: $Date$