From 8036ca47e27c22055cf8d708358b2e48b2a63e3b Mon Sep 17 00:00:00 2001 From: Duncan Sands Date: Fri, 30 Mar 2007 12:22:09 +0000 Subject: [PATCH] Various hopefully correct easy fixes. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@35506 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/AliasAnalysis.html | 2 +- docs/DeveloperPolicy.html | 2 +- docs/ExceptionHandling.html | 6 +++--- docs/GarbageCollection.html | 2 +- docs/LangRef.html | 19 +++++++++---------- docs/ProgrammersManual.html | 6 +++--- docs/SystemLibrary.html | 2 +- 7 files changed, 19 insertions(+), 20 deletions(-) diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html index 63567876e37..b1163e0633b 100644 --- a/docs/AliasAnalysis.html +++ b/docs/AliasAnalysis.html @@ -70,7 +70,7 @@ memory. There are many different algorithms for alias analysis and many different ways of classifying them: flow-sensitive vs flow-insensitive, context-sensitive vs context-insensitive, field-sensitive vs field-insensitive, unification-based vs subset-based, etc. Traditionally, alias analyses respond -to a query with a Must, May, or No alias response, +to a query with a Must, May, or No alias response, 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.

diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index db112af1a73..85b8aab2c1b 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -162,7 +162,7 @@ bug being fixed or feature being implemented is in the llvm-gcc C++ front-end, in which case it must be written in C++).
  • Test cases, especially for regressions, should be reduced as much as - possible, by bugpoint or + possible, by bugpoint or manually. It is unacceptable to place an entire failing program into llvm/test as this creates a time-to-test burden on all developers. Please keep them short.
  • diff --git a/docs/ExceptionHandling.html b/docs/ExceptionHandling.html index d515b4cd0ed..a0ecbfd2aae 100644 --- a/docs/ExceptionHandling.html +++ b/docs/ExceptionHandling.html @@ -22,10 +22,10 @@
    1. Throw
    2. Try/Catch
    3. -
    4. Finallys
    5. +
    6. Finallys
    7. Throw Filters
    -
  • Exception Handling Intrinsics +
  • Exception Handling Intrinsics
    1. llvm.eh.exception
    2. llvm.eh.selector
    3. @@ -281,7 +281,7 @@ exception structure.

      diff --git a/docs/GarbageCollection.html b/docs/GarbageCollection.html index 91be2396746..f2f37229924 100644 --- a/docs/GarbageCollection.html +++ b/docs/GarbageCollection.html @@ -387,7 +387,7 @@ The llvm_cg_walk_gcroots function is a function provided by the code generator that iterates through all of the GC roots on the stack, calling the specified function pointer with each record. For each GC root, the address of the pointer and the meta-data (from the llvm.gcroot intrinsic) are provided. +href="#roots">llvm.gcroot intrinsic) are provided.

      diff --git a/docs/LangRef.html b/docs/LangRef.html index 11b43befdff..4342445ec6c 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -27,7 +27,6 @@
    4. Parameter Attributes
    5. Module-Level Inline Assembly
    6. Data Layout
    7. -
    8. Check Points
  • Type System @@ -886,7 +885,7 @@ system. The current set of primitive types is as follows:

    - + @@ -1714,7 +1713,7 @@ continued at the dynamically nearest "exception" label.

    1. - The optional "cconv" marker indicates which calling + The optional "cconv" marker indicates which calling convention the call should use. If none is specified, the call defaults to using C calling conventions.
    2. @@ -2966,8 +2965,8 @@ type must be smaller than the destination type.

      Semantics:

      The 'fpext' instruction extends the value from a smaller -floating point type to a larger -floating point type. The fpext cannot be +floating point type to a larger +floating point type. The fpext cannot be used to make a no-op cast because it always changes bits. Use bitcast to make a no-op cast for a floating point cast.

      @@ -3140,7 +3139,7 @@ the integer type ty2.

      Arguments:

      The 'ptrtoint' instruction takes a value to cast, which -must be a pointer value, and a type to cast it to +must be a pointer value, and a type to cast it to ty2, which must be an integer type.

      Semantics:
      @@ -3174,7 +3173,7 @@ are the same size, then nothing is done (no-op cast).

      a pointer type, ty2.

      Arguments:
      -

      The 'inttoptr' instruction takes an integer +

      The 'inttoptr' instruction takes an integer value to cast, and a type to cast it to, which must be a pointer type. @@ -3490,7 +3489,7 @@ value argument; otherwise, it returns the second value argument. href="#i_ret">ret instruction.

    3. -

      The optional "cconv" marker indicates which calling +

      The optional "cconv" marker indicates which calling convention the call should use. If none is specified, the call defaults to using C calling conventions.

    4. @@ -3747,7 +3746,7 @@ The second argument is a pointer to a va_list element to copy from.

      The 'llvm.va_copy' intrinsic works just like the va_copy macro available in C. In a target-dependent way, it copies the source va_list element into the destination list. This intrinsic is necessary -because the llvm.va_begin intrinsic may be +because the llvm.va_start intrinsic may be arbitrarily complex and require memory allocation, for example.

      @@ -4029,7 +4028,7 @@ that were allocated after the llvm.stacksave was executed.

      The 'llvm.stackrestore' intrinsic is used to restore the state of the function stack to the state it was in when the corresponding llvm.stacksave intrinsic executed. This is +href="#i_stacksave">llvm.stacksave intrinsic executed. This is useful for implementing language features like scoped automatic variable sized arrays in C99.

      diff --git a/docs/ProgrammersManual.html b/docs/ProgrammersManual.html index 9661b769357..347861e9638 100644 --- a/docs/ProgrammersManual.html +++ b/docs/ProgrammersManual.html @@ -2195,7 +2195,7 @@ the lib/VMCore directory.

      point type.
      StructType
      Subclass of DerivedTypes for struct types.
      -
      FunctionType
      +
      FunctionType
      Subclass of DerivedTypes for function types.
      • bool isVarArg() const: Returns true if its a vararg @@ -2389,7 +2389,7 @@ method. In addition, all LLVM values can be named. The "name" of the -

        The name of this instruction is "foo". NOTE +

        The name of this instruction is "foo". NOTE that the name of any value may be missing (an empty string), so names should ONLY be used for debugging (making the source code easier to read, debugging printouts), they should not be used to keep track of values or map @@ -2805,7 +2805,7 @@ is its address (after linking) which is guaranteed to be constant.

        create and what type of linkage the function should have. The FunctionType argument specifies the formal arguments and return value for the function. The same - FunctionType value can be used to + FunctionType value can be used to create multiple functions. The Parent argument specifies the Module in which the function is defined. If this argument is provided, the function will automatically be inserted into that module's list of diff --git a/docs/SystemLibrary.html b/docs/SystemLibrary.html index 4dba5bc6a45..b02c7869d77 100644 --- a/docs/SystemLibrary.html +++ b/docs/SystemLibrary.html @@ -32,7 +32,7 @@
      -

      Written by Reid Spencer

      +

      Written by Reid Spencer

      -- 2.34.1
    TypeDescription
    voidNo value
    voidNo value
    i88-bit value
    i3232-bit value
    float32-bit floating point value