From gaeke at cs.uiuc.edu Mon May 31 00:53:04 2004 From: gaeke at cs.uiuc.edu (Brian Gaeke) Date: Mon May 31 00:53:04 2004 Subject: [llvm-commits] CVS: reopt/include/reopt/UnpackTraceFunction.h Message-ID: <200405310551.AAA27334@kain.cs.uiuc.edu> Changes in directory reopt/include/reopt: UnpackTraceFunction.h updated: 1.5 -> 1.6 --- Log message: Update some comments. --- Diffs of the changes: (+5 -5) Index: reopt/include/reopt/UnpackTraceFunction.h diff -u reopt/include/reopt/UnpackTraceFunction.h:1.5 reopt/include/reopt/UnpackTraceFunction.h:1.6 --- reopt/include/reopt/UnpackTraceFunction.h:1.5 Sun May 30 14:39:49 2004 +++ reopt/include/reopt/UnpackTraceFunction.h Mon May 31 00:51:42 2004 @@ -29,17 +29,17 @@ TargetMachine *TM; TraceFunction *TF; - /// Static stack size of the MachineFunction. Filled in by rewriteProlog () - /// by calling getStaticStackSize (), and then used again by rewriteEpilog (). + /// Static stack size of the MachineFunction. Filled in + /// by getStaticStackSize (), and then used by rewriteProlog & rewriteEpilog. /// unsigned StaticStackSize; - /// Total stack size of the MachineFunction, including space for regs - /// modified in TraceFn to be saved. + /// Total stack size of the MachineFunction, including space to save regs + /// modified in TraceFn. /// int TotalStackSize; - /// Registers clobbered in the trace. Filled in by findRegsUsedInFunction (). + /// Registers clobbered in the trace. Filled in by findRegsToSave. /// std::set RegsToSave; From gaeke at cs.uiuc.edu Mon May 31 00:54:02 2004 From: gaeke at cs.uiuc.edu (Brian Gaeke) Date: Mon May 31 00:54:02 2004 Subject: [llvm-commits] CVS: reopt/lib/LightWtProfiling/ValueAllocState.cpp Message-ID: <200405310551.AAA27442@kain.cs.uiuc.edu> Changes in directory reopt/lib/LightWtProfiling: ValueAllocState.cpp updated: 1.1 -> 1.2 --- Log message: Refactor the calculation of InstructionKey & OperandKey into getValueAllocStateKeys(). Make it understand that the first PHI node in a trace should have a special key. --- Diffs of the changes: (+37 -30) Index: reopt/lib/LightWtProfiling/ValueAllocState.cpp diff -u reopt/lib/LightWtProfiling/ValueAllocState.cpp:1.1 reopt/lib/LightWtProfiling/ValueAllocState.cpp:1.2 --- reopt/lib/LightWtProfiling/ValueAllocState.cpp:1.1 Sun May 30 04:01:28 2004 +++ reopt/lib/LightWtProfiling/ValueAllocState.cpp Mon May 31 00:51:44 2004 @@ -17,6 +17,7 @@ #include "reopt/MappingInfo.h" #include "llvm/Module.h" #include "llvm/Argument.h" +#include "llvm/iPHINode.h" #include "llvm/Support/InstIterator.h" #include "Support/Debug.h" #include "../../../../lib/Target/SparcV9/RegAlloc/AllocInfo.h" @@ -85,26 +86,42 @@ abort (); } +static BasicBlock *TraceEntryBB = 0; + +/// getValueAllocStateKeys - Fill in InstructionKey and OperandKey with the +/// indices used to look up saved register allocation state for V in F. +/// +static void getValueAllocStateKeys (Function *F, Value *V, int &InstructionKey, + int &OperandKey, bool preferLiveIn) { + if (Argument *Arg = dyn_cast (V)) { + InstructionKey = -1; + OperandKey = getNumberOfFunctionArg (F, Arg); + } else if (Instruction *Inst = dyn_cast (V)) { + InstructionKey = getSavedStateIndexOfInstruction (F, Inst); + if (isa (Inst) && preferLiveIn + && Inst->getParent() == TraceEntryBB) + OperandKey = -2; // look for PhiCpRes + else + OperandKey = -1; + } else { + std::cerr << "getValueAllocStateKeys: can't look up state for " << *V; + abort(); + } +} + /// Returns the register number or stack position where V can be found in the /// machine code for the function F, which it finds by searching the global /// variable _llvm_regAllocState written out by PhyRegAlloc.cpp during a /// previous invocation of llc. /// -static AllocInfo getValueAllocStateFromModule (Function *F, Value *V) { +static AllocInfo getValueAllocStateFromModule (Function *F, Value *V, + bool preferLiveIn) { unsigned FI = getLLVMFunctionPositionInfo (F); FunctionAllocState *FAllocState = _llvm_regAllocState.functions[FI]; assert (FAllocState->numTuples > 0 && "Reg. alloc state for function is empty"); int InstructionKey = -1, OperandKey = -1; - if (Argument *A = dyn_cast (V)) { - // Find the alloc state of an argument. - OperandKey = getNumberOfFunctionArg (F, A); - } else { - // Figure out the indices (FI, VI, VO) that can be used to look up V, which - // is an operand of some instruction in F, in _llvm_regAllocState: - Instruction *Instr = cast (V); - InstructionKey = getSavedStateIndexOfInstruction (F, Instr); - } + getValueAllocStateKeys (F, V, InstructionKey, OperandKey, preferLiveIn); // Reconstruct the AllocInfo for V by searching // _llvm_regAllocState.functions[FI] for a tuple that starts with // (InstructionKey, OperandKey, ...): @@ -121,7 +138,7 @@ } // By this time we had better have found it, otherwise we are about to do bad // things. - std::cerr << "ERROR: UnpackTraceFunction: No saved AllocInfo found for " + std::cerr << "ERROR: No saved AllocInfo found for " << F->getName () << "()'s value " << *V << " in getValueAllocStateFromModule()\n"; abort (); @@ -131,26 +148,13 @@ /// machine code for the function F, which it finds by searching the global /// variable ExportedFnAllocState exported by PhyRegAlloc.cpp. /// -static AllocInfo getValueAllocStateFromGlobal (Function *F, Value *V) { +static AllocInfo getValueAllocStateFromGlobal (Function *F, Value *V, + bool preferLiveIn) { // Get the saved PhyRegAlloc state for F out of ExportedFnAllocState: std::vector &FState = ExportedFnAllocState[F]; assert (FState.size () > 0 && "Reg. alloc state for function is empty"); int InstructionKey = -1, OperandKey = -1; - if (Argument *A = dyn_cast (V)) { - // Find the alloc state of an argument. - OperandKey = getNumberOfFunctionArg (F, A); - } else { - if (! isa (V)) { - std::cerr - << "ERROR: Don't know how to look up alloc state for this Value:\n\t" - << *V << "\n"; - abort (); - } - // Figure out the indices (VI, VO) that can be used to look up V, - // which is some instruction producing a value in F, in FState: - Instruction *Instr = cast (V); - InstructionKey = getSavedStateIndexOfInstruction (F, Instr); - } + getValueAllocStateKeys (F, V, InstructionKey, OperandKey, preferLiveIn); // Reconstruct the AllocInfo for V by searching // FState for a tuple that starts with (InstructionKey, OperandKey, ...): for (unsigned i = 0, s = FState.size (); i < s; ++i) { @@ -164,7 +168,7 @@ } // By this time we had better have found it, otherwise we are about to do bad // things. - std::cerr << "ERROR: UnpackTraceFunction: No saved AllocInfo found for " + std::cerr << "ERROR: No saved AllocInfo found for " << F->getName () << "()'s value " << *V << " in getValueAllocStateFromGlobal()\n"; abort (); @@ -175,9 +179,12 @@ /// std::pair GetValueAllocState (TraceFunction *TF, Value *V, bool preferLiveIn) { - return std::make_pair (getValueAllocStateFromModule (TF->MatrixFn, V), + TraceEntryBB = TF->T.getEntryBasicBlock(); + return std::make_pair + (getValueAllocStateFromModule (TF->MatrixFn, V, preferLiveIn), getValueAllocStateFromGlobal (TF->TraceFn, - TF->getCorrespondingValue (V, preferLiveIn))); + TF->getCorrespondingValue (V, preferLiveIn), + preferLiveIn)); } } // end namespace llvm From gaeke at cs.uiuc.edu Mon May 31 00:54:10 2004 From: gaeke at cs.uiuc.edu (Brian Gaeke) Date: Mon May 31 00:54:10 2004 Subject: [llvm-commits] CVS: reopt/lib/TraceToFunction/TraceToFunction.cpp Message-ID: <200405310551.AAA27455@kain.cs.uiuc.edu> Changes in directory reopt/lib/TraceToFunction: TraceToFunction.cpp updated: 1.58 -> 1.59 --- Log message: Add a timer. --- Diffs of the changes: (+2 -0) Index: reopt/lib/TraceToFunction/TraceToFunction.cpp diff -u reopt/lib/TraceToFunction/TraceToFunction.cpp:1.58 reopt/lib/TraceToFunction/TraceToFunction.cpp:1.59 --- reopt/lib/TraceToFunction/TraceToFunction.cpp:1.58 Mon May 24 15:36:10 2004 +++ reopt/lib/TraceToFunction/TraceToFunction.cpp Mon May 31 00:51:45 2004 @@ -38,6 +38,7 @@ #include "Support/StringExtras.h" // for utostr() #define DEBUG_TYPE "tracetofunction" #include "Support/Debug.h" // for DEBUG() +#include "Support/Timer.h" #include namespace llvm { @@ -750,6 +751,7 @@ /// data structures. /// TraceFunction *TraceFunction::get (Trace &T) { + NamedRegionTimer X ("TraceToFunction"); TraceFunctionBuilder TTF; return TTF.buildTraceFunction (T); } From llvm at cs.uiuc.edu Mon May 31 16:04:02 2004 From: llvm at cs.uiuc.edu (LLVM) Date: Mon May 31 16:04:02 2004 Subject: [llvm-commits] CVS: llvm/utils/NightlyTest.pl Message-ID: <200405312100.QAA18891@zion.cs.uiuc.edu> Changes in directory llvm/utils: NightlyTest.pl updated: 1.47 -> 1.48 --- Log message: Clean up the Feature and Regression test output to (a) use section headers, (b) avoid
 tag so page width doesn't become excessive, (c) omit the
execution time stats, (d) format each reported test in a list with bold
headings for readability, (e) omit long lines of dashes.


---
Diffs of the changes:  (+35 -10)

Index: llvm/utils/NightlyTest.pl
diff -u llvm/utils/NightlyTest.pl:1.47 llvm/utils/NightlyTest.pl:1.48
--- llvm/utils/NightlyTest.pl:1.47	Sat May 29 19:17:47 2004
+++ llvm/utils/NightlyTest.pl	Mon May 31 15:59:55 2004
@@ -272,27 +272,52 @@
   if (open SRCHFILE, $filename) {
     # Skip stuff before ---TEST RESULTS
     while (  ) {
-      if ( m/^--- TEST RESULTS/ ) { 
-	  push(@lines, $_); last; 
-      }
+      if ( m/^--- TEST RESULTS/ ) { last; }
     }
     # Process test results
+    push(@lines,"

TEST RESULTS

  1. \n"); + my $first_list = 1; + my $should_break = 1; while ( ) { if ( length($_) > 1 ) { - if ( ! m/: PASS[ ]*$/ && - ! m/^ qmtest.target:/ && - ! m/^ local/ && - ! m/^gmake:/ ) { - push(@lines,$_); + chomp($_); + if ( ! m/: PASS[ ]*$/ && + ! m/^ qmtest.target:/ && + ! m/^ local/ && + ! m/^gmake:/ ) { + if ( m/: XFAIL/ || m/: XPASS/ || m/: FAIL/ ) { + if ( $first_list ) { + $first_list = 0; + $should_break = 1; + push(@lines,"$_
    \n"); + } else { + push(@lines,"
  2. $_
    \n"); + } + } elsif ( m/^--- STATISTICS/ ) { + if ( $first_list ) { push(@lines,"PERFECT!"); } + push(@lines,"

STATISTICS

\n");
+	    $should_break = 0;
+	  } elsif ( m/^--- TESTS WITH/ ) {
+	    $should_break = 1;
+	    $first_list = 1;
+	    push(@lines,"

TESTS WITH UNEXPECTED RESULTS

  1. \n"); + } elsif ( m/^real / ) { + last; + } else { + if ( $should_break ) { + push(@lines,"$_
    \n"); + } else { + push(@lines,"$_\n"); + } + } } } } close SRCHFILE; } my $content = join("", at lines); - return "
    \n at lines
    \n"; + return "$content
\n"; } - # Get results of feature tests. my $FeatureTestResults; # String containing the results of the feature tests From llvm at cs.uiuc.edu Mon May 31 16:43:01 2004 From: llvm at cs.uiuc.edu (LLVM) Date: Mon May 31 16:43:01 2004 Subject: [llvm-commits] CVS: llvm/utils/NightlyTestTemplate.html Message-ID: <200405312139.QAA19012@zion.cs.uiuc.edu> Changes in directory llvm/utils: NightlyTestTemplate.html updated: 1.24 -> 1.25 --- Log message: Align the lower portion of the page with the left margin so that the page width is not made excessive by the large table of results. Improves readability of the page. --- Diffs of the changes: (+2 -2) Index: llvm/utils/NightlyTestTemplate.html diff -u llvm/utils/NightlyTestTemplate.html:1.24 llvm/utils/NightlyTestTemplate.html:1.25 --- llvm/utils/NightlyTestTemplate.html:1.24 Fri May 28 15:30:23 2004 +++ llvm/utils/NightlyTestTemplate.html Mon May 31 16:38:56 2004 @@ -108,11 +108,11 @@
  • Newly passing tests: $TestsFixed
  • Newly failing tests: $TestsBroken - +

    Changes over Time +Changes Over Time

    From lattner at cs.uiuc.edu Tue Jun 1 01:52:01 2004 From: lattner at cs.uiuc.edu (Chris Lattner) Date: Tue Jun 1 01:52:01 2004 Subject: [llvm-commits] CVS: llvm/docs/CodeGenerator.html Message-ID: <200406010648.BAA22176@zion.cs.uiuc.edu> Changes in directory llvm/docs: CodeGenerator.html added (r1.1) --- Log message: It's a small start, but it is certainly needed. Contributions are certainly welcomed. :) --- Diffs of the changes: (+348 -0) Index: llvm/docs/CodeGenerator.html diff -c /dev/null llvm/docs/CodeGenerator.html:1.1 *** /dev/null Tue Jun 1 01:48:10 2004 --- llvm/docs/CodeGenerator.html Tue Jun 1 01:48:00 2004 *************** *** 0 **** --- 1,348 ---- + + + + The LLVM Target-Independent Code Generator + + + + +

    + The LLVM Target-Independent Code Generator +
    + +
      +
    1. Introduction + +
    2. +
    3. Target description classes + +
    4. +
    5. Machine code description classes +
    6. +
    7. Target-independent code generation algorithms +
    8. +
    9. Target description implementations +
    + +
    +

    Written by Chris Lattner

    +
    + + + + + +
    + +

    The LLVM target-independent code generator is a framework that provides a + suite of reusable components for translating the LLVM internal representation to + the machine code for a specified target -- either in assembly form (suitable for + a static compiler) or in binary machine code format (usable for a JIT compiler). + The LLVM target-independent code generator consists of four main components:

    + +
      +
    1. Abstract target description interfaces which + capture improtant properties about various aspects of the machine independently + of how they will be used. These interfaces are defined in + include/llvm/Target/.
    2. + +
    3. Classes used to represent the machine code being + generator for a target. These classes are intended to be abstract enough to + represent the machine code for any target machine. These classes are + defined in include/llvm/CodeGen/.
    4. + +
    5. Target-independent algorithms used to implement + various phases of native code generation (register allocation, scheduling, stack + frame representation, etc). This code lives in lib/CodeGen/.
    6. + +
    7. Implementations of the abstract target description + interfaces for particular targets. These machine descriptions make use of + the components provided by LLVM, and can optionally provide custom + target-specific passes, to build complete code generators for a specific target. + Target descriptions live in lib/Target/.
    8. + +
    + +

    + Depending on which part of the code generator you are interested in working on, + different pieces of this will be useful to you. In any case, you should be + familiar with the target description and machine code representation classes. If you want to add + a backend for a new target, you will need implement the + targe description classes for your new target and understand the LLVM code representation. If you are interested in + implementing a new code generation algorithm, it + should only depend on the target-description and machine code representation + classes, ensuring that it is portable. +

    + +
    + + + + +
    + +

    The two pieces of the LLVM code generator are the high-level interface to the + code generator and the set of reusable components that can be used to build + target-specific backends. The two most important interfaces (TargetMachine and TargetData classes) are the only ones that are + required to be defined for a backend to fit into the LLVM system, but the others + must be defined if the reusable code generator components are going to be + used.

    + +

    This design has two important implications. The first is that LLVM can + support completely non-traditional code generation targets. For example, the C + backend does not require register allocation, instruction selection, or any of + the other standard components provided by the system. As such, it only + implements these two interfaces, and does its own thing. Another example of a + code generator like this is a (purely hypothetical) backend that converts LLVM + to the GCC RTL form and uses GCC to emit machine code for a target.

    + +

    The other implication of this design is that it is possible to design and + implement radically different code generators in the LLVM system that do not + make use of any of the built-in components. Doing so is not recommended at all, + but could be required for radically different targets that do not fit into the + LLVM machine description model: programmable FPGAs for example.

    +

    +
    + + +
  • + + +
    + +

    The LLVM target-indendent code generator is designed to support efficient and + quality code generation for standard register-based microprocessors. Code + generation in this model is divided into the following stages:

    + +
      +
    1. Instruction Selection - Determining a efficient implementation of the + input LLVM code in the target instruction set. This stage produces the initial + code for the program in the target instruction set the makes use of virtual + registers in SSA form and physical registers that represent any required + register assignments due to target constraints or calling conventions.
    2. + +
    3. SSA-based Machine Code Optimizations - This (optional) stage consists + of a series of machine-code optimizations that operate on the SSA-form produced + by the instruction selector. Optimizations like modulo-scheduling, normal + scheduling, or peephole optimization work here.
    4. + +
    5. Register Allocation - The target code is transformed from an infinite + virtual register file in SSA form to the concrete register file used by the + target. This phase introduces spill code and eliminates all virtual register + references from the program.
    6. + +
    7. Prolog/Epilog Code Insertion - Once the machine code has been + generated for the function and the amount of stack space required is known (used + for LLVM alloca's and spill slots), the prolog and epilog code for the function + can be inserted and "abstract stack location references" can be eliminated. + This stage is responsible for implementing optimizations like frame-pointer + elimination and stack packing.
    8. + +
    9. Late Machine Code Optimizations - Optimizations that operate on + "final" machine code can go here, such as spill code scheduling and peephole + optimizations.
    10. + +
    11. Code Emission - The final stage actually outputs the machine code for + the current function, either in the target assembler format or in machine + code.
    12. + +
    + +

    + The code generator is based on the assumption that the instruction selector will + use an optimal pattern matching selector to create high-quality sequences of + native code. Alternative code generator designs based on pattern expansion and + aggressive iterative peephole optimization are much slower. This design is + designed to permit efficient compilation (important for JIT environments) and + aggressive optimization (used when generate code offline) by allowing components + of varying levels of sophisication to be used for any step of compilation.

    + +

    + In addition to these stages, target implementations can insert arbitrary + target-specific passes into the flow. For example, the X86 target uses a + special pass to handle the 80x87 floating point stack architecture. Other + targets with unusual requirements can be supported with custom passes as needed. +

    + +
    + + + + + +
    + +

    The target description classes require a detailed descriptions of the target + architecture. These target descriptions often have a large amount of common + information (e.g., an add instruction is almost identical to a sub instruction). + In order to allow the maximum amount of commonality to be factored out, the LLVM + code generator uses the TableGen tool to + allow +

    + +
    + + + + + +
    + +

    The LLVM target description classes (which are located in the + include/llvm/Target directory) provide an abstract description of the + target machine, independent of any particular client. These classes are + designed to capture the abstract properties of the target (such as what + instruction and registers it has), and do not incorporate any particular pieces + of code generation algorithms (these interfaces do not take interference graphs + as inputs or other algorithm-specific data structures).

    + +

    All of the target description classes (except the TargetData class) are designed to be subclassed by + the concrete target implementation, and have virtual methods implemented. To + get to these implementations, TargetMachine class provides accessors that + should be implemented by the target.

    + +
    + + + + +
    + +

    The TargetMachine class provides virtual methods that are used to + access the target-specific implementations of the various target description + classes (with the getInstrInfo, getRegisterInfo, + getFrameInfo, ... methods). This class is designed to be subclassed by + a concrete target implementation (e.g., X86TargetMachine) which + implements the various virtual methods. The only required target description + class is the TargetData class, but if the + code generator components are to be used, the other interfaces should be + implemented as well.

    + +
    + + + + + +
    + +

    The TargetData class is the only required target description class, + and it is the only class that is not extensible (it cannot be derived from). It + specifies information about how the target lays out memory for structures, the + alignment requirements for various data types, the size of pointers in the + target, and whether the target is little- or big-endian.

    + +
    + + + + + +
    + +

    The MRegisterInfo class (which will eventually be renamed to + TargetRegisterInfo) is used to describe the register file of the + target and any interactions between the registers.

    + +

    Registers in the code generator are represented in the code generator by + unsigned numbers. Physical registers (those that actually exist in the target + description) are unique small numbers, and virtual registers are generally + large.

    + +

    Each register in the processor description has an associated + MRegisterDesc entry, which provides a textual name for the register + (used for assembly output and debugging dumps), a set of aliases (used to + indicate that one register overlaps with another), and some flag bits. +

    + +

    In addition to the per-register description, the MRegisterInfo class + exposes a set of processor specific register classes (instances of the + TargetRegisterClass class). Each register class contains sets of + registers that have the same properties (for example, they are all 32-bit + integer registers). Each SSA virtual register created by the instruction + selector has an associated register class. When the register allocator runs, it + replaces virtual registers with a physical register in the set.

    + +

    + The target-specific implementations of these classes is auto-generated from a TableGen description of the register file. +

    + +
    + + + + + + + + + + + + + + + + + +
    +
    + Valid CSS! + Valid HTML 4.01! + + Chris Lattner
    + The LLVM Compiler Infrastructure
    + Last modified: $Date: 2004/06/01 06:48:00 $ +
    + + + From criswell at cs.uiuc.edu Tue Jun 1 09:55:01 2004 From: criswell at cs.uiuc.edu (John Criswell) Date: Tue Jun 1 09:55:01 2004 Subject: [llvm-commits] CVS: llvm/lib/VMCore/AsmWriter.cpp Message-ID: <200406011454.JAA20407@choi.cs.uiuc.edu> Changes in directory llvm/lib/VMCore: AsmWriter.cpp updated: 1.133 -> 1.134 --- Log message: Modified calcTypeName() so that it does not allocate a std::string for every recursive call. This makes it more robust for deeply nested, unnamed types. --- Diffs of the changes: (+37 -24) Index: llvm/lib/VMCore/AsmWriter.cpp diff -u llvm/lib/VMCore/AsmWriter.cpp:1.133 llvm/lib/VMCore/AsmWriter.cpp:1.134 --- llvm/lib/VMCore/AsmWriter.cpp:1.133 Thu May 27 17:04:46 2004 +++ llvm/lib/VMCore/AsmWriter.cpp Tue Jun 1 09:54:08 2004 @@ -224,18 +224,26 @@ -static std::string calcTypeName(const Type *Ty, - std::vector &TypeStack, - std::map &TypeNames){ - if (Ty->isPrimitiveType() && !isa(Ty)) - return Ty->getDescription(); // Base case +static void calcTypeName(const Type *Ty, + std::vector &TypeStack, + std::map &TypeNames, + std::string & Result){ + if (Ty->isPrimitiveType() && !isa(Ty)) { + Result += Ty->getDescription(); // Base case + return; + } // Check to see if the type is named. std::map::iterator I = TypeNames.find(Ty); - if (I != TypeNames.end()) return I->second; + if (I != TypeNames.end()) { + Result += I->second; + return; + } - if (isa(Ty)) - return "opaque"; + if (isa(Ty)) { + Result += "opaque"; + return; + } // Check to see if the Type is already on the stack... unsigned Slot = 0, CurSize = TypeStack.size(); @@ -244,21 +252,23 @@ // This is another base case for the recursion. In this case, we know // that we have looped back to a type that we have previously visited. // Generate the appropriate upreference to handle this. - if (Slot < CurSize) - return "\\" + utostr(CurSize-Slot); // Here's the upreference + if (Slot < CurSize) { + Result += "\\" + utostr(CurSize-Slot); // Here's the upreference + return; + } TypeStack.push_back(Ty); // Recursive case: Add us to the stack.. - std::string Result; switch (Ty->getPrimitiveID()) { case Type::FunctionTyID: { const FunctionType *FTy = cast(Ty); - Result = calcTypeName(FTy->getReturnType(), TypeStack, TypeNames) + " ("; + calcTypeName(FTy->getReturnType(), TypeStack, TypeNames, Result); + Result += " ("; for (FunctionType::param_iterator I = FTy->param_begin(), E = FTy->param_end(); I != E; ++I) { if (I != FTy->param_begin()) Result += ", "; - Result += calcTypeName(*I, TypeStack, TypeNames); + calcTypeName(*I, TypeStack, TypeNames, Result); } if (FTy->isVarArg()) { if (FTy->getNumParams()) Result += ", "; @@ -269,35 +279,37 @@ } case Type::StructTyID: { const StructType *STy = cast(Ty); - Result = "{ "; + Result += "{ "; for (StructType::element_iterator I = STy->element_begin(), E = STy->element_end(); I != E; ++I) { if (I != STy->element_begin()) Result += ", "; - Result += calcTypeName(*I, TypeStack, TypeNames); + calcTypeName(*I, TypeStack, TypeNames, Result); } Result += " }"; break; } case Type::PointerTyID: - Result = calcTypeName(cast(Ty)->getElementType(), - TypeStack, TypeNames) + "*"; + calcTypeName(cast(Ty)->getElementType(), + TypeStack, TypeNames, Result); + Result += "*"; break; case Type::ArrayTyID: { const ArrayType *ATy = cast(Ty); - Result = "[" + utostr(ATy->getNumElements()) + " x "; - Result += calcTypeName(ATy->getElementType(), TypeStack, TypeNames) + "]"; + Result += "[" + utostr(ATy->getNumElements()) + " x "; + calcTypeName(ATy->getElementType(), TypeStack, TypeNames, Result); + Result += "]"; break; } case Type::OpaqueTyID: - Result = "opaque"; + Result += "opaque"; break; default: - Result = ""; + Result += ""; } TypeStack.pop_back(); // Remove self from stack... - return Result; + return; } @@ -321,9 +333,10 @@ // names. // std::vector TypeStack; - std::string TypeName = calcTypeName(Ty, TypeStack, TypeNames); + std::string TypeName; + calcTypeName(Ty, TypeStack, TypeNames, TypeName); TypeNames.insert(std::make_pair(Ty, TypeName));//Cache type name for later use - return Out << TypeName; + return (Out << TypeName); } From lattner at cs.uiuc.edu Tue Jun 1 12:22:02 2004 From: lattner at cs.uiuc.edu (Chris Lattner) Date: Tue Jun 1 12:22:02 2004 Subject: [llvm-commits] CVS: llvm/docs/CodeGenerator.html Message-ID: <200406011718.MAA02176@zion.cs.uiuc.edu> Changes in directory llvm/docs: CodeGenerator.html updated: 1.1 -> 1.2 --- Log message: Add a warning about incompleteness, fix validation errors --- Diffs of the changes: (+12 -9) Index: llvm/docs/CodeGenerator.html diff -u llvm/docs/CodeGenerator.html:1.1 llvm/docs/CodeGenerator.html:1.2 --- llvm/docs/CodeGenerator.html:1.1 Tue Jun 1 01:48:00 2004 +++ llvm/docs/CodeGenerator.html Tue Jun 1 12:18:11 2004 @@ -36,7 +36,7 @@
  • Target description implementations
  • @@ -45,6 +45,10 @@

    Written by Chris Lattner

    +
    +

    Warning: This is a work in progress.

    +
    +
    Introduction @@ -126,12 +130,11 @@ make use of any of the built-in components. Doing so is not recommended at all, but could be required for radically different targets that do not fit into the LLVM machine description model: programmable FPGAs for example.

    -

    @@ -195,7 +198,7 @@
    @@ -273,7 +276,7 @@
    @@ -310,17 +313,17 @@ @@ -341,7 +344,7 @@ Chris Lattner
    The LLVM Compiler Infrastructure
    - Last modified: $Date: 2004/06/01 06:48:00 $ + Last modified: $Date: 2004/06/01 17:18:11 $ From lattner at cs.uiuc.edu Tue Jun 1 12:34:03 2004 From: lattner at cs.uiuc.edu (Chris Lattner) Date: Tue Jun 1 12:34:03 2004 Subject: [llvm-commits] CVS: llvm-gcc/gcc/gensupport.c Message-ID: <200406011729.MAA02387@zion.cs.uiuc.edu> Changes in directory llvm-gcc/gcc: gensupport.c updated: 1.1.1.1 -> 1.2 --- Log message: Fix the gen* utilities that GCC used when running under cygwin. They were reading the .md files and getting confused about the \r characters that windows has in them. This forces cygwin to open the files in "text" mode. --- Diffs of the changes: (+3 -3) Index: llvm-gcc/gcc/gensupport.c diff -u llvm-gcc/gcc/gensupport.c:1.1.1.1 llvm-gcc/gcc/gensupport.c:1.2 --- llvm-gcc/gcc/gensupport.c:1.1.1.1 Thu Jan 8 15:58:40 2004 +++ llvm-gcc/gcc/gensupport.c Tue Jun 1 12:29:16 2004 @@ -205,7 +205,7 @@ static const char sep[2] = { DIR_SEPARATOR, '\0' }; pathname = concat (stackp->fname, sep, filename, NULL); - input_file = fopen (pathname, "r"); + input_file = fopen (pathname, "rt"); if (input_file != NULL) goto success; free (pathname); @@ -216,7 +216,7 @@ pathname = concat (base_dir, filename, NULL); else pathname = xstrdup (filename); - input_file = fopen (pathname, "r"); + input_file = fopen (pathname, "rt"); if (input_file == NULL) { free (pathname); @@ -917,7 +917,7 @@ base_dir = save_string (filename, lastsl - filename + 1 ); read_rtx_filename = filename; - input_file = fopen (filename, "r"); + input_file = fopen (filename, "rt"); if (input_file == 0) { perror (filename); From brukman at cs.uiuc.edu Tue Jun 1 12:39:02 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 12:39:02 2004 Subject: [llvm-commits] CVS: llvm/docs/doxygen.footer Message-ID: <200406011735.MAA10185@zion.cs.uiuc.edu> Changes in directory llvm/docs: doxygen.footer updated: 1.1 -> 1.2 --- Log message: * It's now the year 2004 * Our main page is index.html, not index.php * Wrap lines at 80 cols --- Diffs of the changes: (+6 -3) Index: llvm/docs/doxygen.footer diff -u llvm/docs/doxygen.footer:1.1 llvm/docs/doxygen.footer:1.2 --- llvm/docs/doxygen.footer:1.1 Wed Dec 31 00:47:28 2003 +++ llvm/docs/doxygen.footer Tue Jun 1 12:35:10 2004 @@ -2,8 +2,11 @@ From brukman at cs.uiuc.edu Tue Jun 1 12:43:03 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 12:43:03 2004 Subject: [llvm-commits] CVS: llvm-www/www-index.html Message-ID: <200406011739.MAA21823@zion.cs.uiuc.edu> Changes in directory llvm-www: www-index.html updated: 1.102 -> 1.103 --- Log message: * Make the text easier to edit by removing leading tabs. * Some changes for HTML 4.01 (Strict) compliance (not complete) --- Diffs of the changes: (+91 -100) Index: llvm-www/www-index.html diff -u llvm-www/www-index.html:1.102 llvm-www/www-index.html:1.103 --- llvm-www/www-index.html:1.102 Fri May 28 02:47:39 2004 +++ llvm-www/www-index.html Tue Jun 1 12:39:07 2004 @@ -2,82 +2,77 @@ - - + -
    + +
    LLVM Overview
    -

    - Low Level Virtual Machine (LLVM) is:

      -
    1. - A compilation strategy - Fundamentally, LLVM is a - compilation strategy designed to enable effective - program optimization across the entire lifetime of a - program. LLVM supports effective optimization at - compile time, link-time (particularly interprocedural), - run-time and offline (i.e., after software is - installed), while remaining transparent to developers - and maintaining compatibility with - existing build scripts.

    2. - -
    3. A virtual - instruction set - LLVM is a low-level object - code representation that uses simple RISC-like - instructions, but provides rich, language-independent, - type information and dataflow - (SSA) information about operands. This combination - enables sophisticated transformations on object code, - while remaining light-weight enough to be attached to - the executable. This combination is key to allowing - link-time, run-time, and offline - transformations.

    4. - -
    5. A compiler - infrastructure - LLVM is also a collection of source - code that implements the language and compilation - strategy. The primary components of the LLVM - infrastructure are a GCC-based C & C++ front-end, a link-time - optimization framework with a growing set of global and - interprocedural analyses and transformations, static - back-ends for the SPARC v9 and X86 architectures, a - back-end which emits portable C code, and a Just-In-Time compiler for - X86 and SPARC v9 processors. See "Current Projects" for - information about other components under - development.

    6. -

    - -

    - LLVM is a robust system, particularly well suited for developing new mid-level - language-independent analyses and optimizations of all sorts, including - those that require - extensive interprocedural analysis. LLVM is also a great target for - front-end development for conventional or - research programming languages, including those which require compile-time, - link-time, or run-time optimization for effective implementation. We - have an incomplete list of projects - which have used LLVM for various purposes, showing that you can get - up-and-running quickly with LLVM, giving time to do interesting things, - even if you only have a semester in a University course. -

    - -

    LLVM is a product of the Lifelong - Code Optimization Project, led by Vikram Adve in the Department of Computer Science at the - University of Illinois, - Urbana-Champaign. Since our public release, LLVM has grown to include - contributions from several - other people! We welcome external contributions, so please send e-mail - to llvmdev at cs.uiuc.edu if you are - interested in contributing code to the LLVM infrastructure. -

    + +
    + +

    Low Level Virtual Machine (LLVM) is:

    + +
      + +
    1. A compilation strategy +designed to enable effective program optimization across the entire lifetime of +a program. LLVM supports effective optimization at compile time, link-time +(particularly interprocedural), run-time and offline (i.e., after software is +installed), while remaining transparent to developers and maintaining +compatibility with existing build scripts.

    2. + +
    3. A virtual instruction set - LLVM +is a low-level object code representation that uses simple RISC-like +instructions, but provides rich, language-independent, type information and +dataflow (SSA) information about operands. This combination enables +sophisticated transformations on object code, while remaining light-weight +enough to be attached to the executable. This combination is key to allowing +link-time, run-time, and offline transformations.

    4. + +
    5. A compiler infrastructure +- LLVM is also a collection of source code that implements the language and +compilation strategy. The primary components of the LLVM infrastructure are a +GCC-based C & C++ front-end, a +link-time optimization framework with a growing set of global and +interprocedural analyses and transformations, static back-ends for the SPARC v9 +and X86 architectures, a back-end which emits portable C code, and a +Just-In-Time compiler for X86 and SPARC v9 processors. See "Current Projects" for information about other +components under development.

    6. + +
    + +

    LLVM is a robust system, particularly well suited for developing new +mid-level language-independent analyses and optimizations of all sorts, +including those that require +extensive interprocedural analysis. LLVM is also a great target for front-end development for conventional or research +programming languages, including those which require compile-time, link-time, or run-time +optimization for effective implementation. We have an incomplete list of projects which have used LLVM for various +purposes, showing that you can get up-and-running quickly with LLVM, giving time +to do interesting things, even if you only have a semester in a University +course.

    + +

    LLVM is a product of the Lifelong Code +Optimization Project, led by Vikram Adve in the Department of Computer Science at the University of Illinois, Urbana-Champaign. Since +our public release, LLVM has grown to include contributions from several +other people! We welcome external contributions, so please send e-mail to +llvmdev at cs.uiuc.edu if you are +interested in contributing code to the LLVM infrastructure.

    + +
    Strengths of the LLVM System
    -

    +

    +
    1. LLVM uses a simple low-level language with strictly defined semantics.
    2. @@ -117,55 +112,51 @@
    3. LLVM is freely available under an OSI-approved "three-clause BSD" license.
    -

    +
    +
    Want to learn more?
    -
    Want to learn more?
    -

    +

    If you'd like to learn more about LLVM, please take a look at the extensive +documentation for LLVM. In particular, all of +the tools distributed with LLVM are described in the LLVM Command Guide. If you're interested in what +source-language features and optimizations we support, please check out the LLVM demo page. If you'd like to browse through the source +code, either check out doxygen or download the most recent release. Finally, if you're +interested in LLVM, have questions, and can't find any answers, please ask on +the LLVM +developer's mailing list.

    - If you'd like to learn more about LLVM, please take a look at the extensive - documentation for LLVM. In particular, all - of the tools distributed with LLVM are described in the LLVM Command Guide. If you're interested in - what source-language features and optimizations we support, please check - out the LLVM demo page. If you'd like to browse through - the source code, either check out doxygen or download the most recent release. Finally, if you're - interested in LLVM, have questions, and can't find any answers, please ask - on the LLVM developer's - mailing list. -

    +
    - - -
    Public LLVM Release!
    -

    - Mar 19, 2004: The LLVM 1.2 is now available for - download! LLVM is publicly available under the OSI-certified +

    Mar 19, 2004: The LLVM 1.2 is now available + for download! LLVM is publicly available under the OSI-certified University of Illinois Open-Source License. See answers to common licensing questions.

    +

    -
    Try out LLVM in your browser
    +

    If you'd like to experiment with LLVM, but don't want to download it and compile it, we've got just the thing for you. You can now compile C and C++ - in your browser, to see what the LLVM representation + in your browser, to see what the LLVM representation looks like, to see what various C/C++ constructs map to in LLVM, and try out some of the optimizers.

    +


    @@ -177,13 +168,13 @@ -

    If you have an addition, please send it in.

    +

    If you have an addition, please send it +in.

    Funding
    -

    - This work is sponsored by the NSF +

    This work is sponsored by the NSF Next Generation Software program through grants EIA-0093426 (an NSF CAREER award) and EIA-0103756. It is also supported in part by the NSF Operating Systems and Compilers program (grant #CCR-9988482), by the From brukman at cs.uiuc.edu Tue Jun 1 13:05:05 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:05:05 2004 Subject: [llvm-commits] CVS: llvm/docs/doxygen.footer Message-ID: <200406011800.NAA01381@zion.cs.uiuc.edu> Changes in directory llvm/docs: doxygen.footer updated: 1.2 -> 1.3 --- Log message: * Add the year 2003 back to the copyright line * Remove doxygen image from page, make LLVM link inline with the text --- Diffs of the changes: (+8 -10) Index: llvm/docs/doxygen.footer diff -u llvm/docs/doxygen.footer:1.2 llvm/docs/doxygen.footer:1.3 --- llvm/docs/doxygen.footer:1.2 Tue Jun 1 12:35:10 2004 +++ llvm/docs/doxygen.footer Tue Jun 1 13:00:39 2004 @@ -1,12 +1,10 @@


    + +Generated on $datetime for LLVM by +doxygen $doxygenversion
    +Copyright © 2003,2004 University of Illinois at Urbana-Champaign. All +Rights Reserved.

    + + + From brukman at cs.uiuc.edu Tue Jun 1 13:14:04 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:14:04 2004 Subject: [llvm-commits] CVS: llvm/docs/doxygen.css Message-ID: <200406011809.NAA12700@zion.cs.uiuc.edu> Changes in directory llvm/docs: doxygen.css updated: 1.1 -> 1.2 --- Log message: Make doxygen pages look like our own documentation. --- Diffs of the changes: (+15 -4) Index: llvm/docs/doxygen.css diff -u llvm/docs/doxygen.css:1.1 llvm/docs/doxygen.css:1.2 --- llvm/docs/doxygen.css:1.1 Wed Dec 31 00:47:28 2003 +++ llvm/docs/doxygen.css Tue Jun 1 13:09:32 2004 @@ -77,8 +77,19 @@ vertical-align: middle; } .title { - font-size: 105% - font-weight: bold; - text-decoration: underline; - text-align: center; + color: black; background: url("img/lines.gif"); + font-family: "Georgia,Palatino,Times,Roman"; font-weight: bold; + border-width: 1px; + border-style: solid none solid none; + text-align: center; + vertical-align: middle; + padding-left: 8pt; + padding-top: 1px; + padding-bottom: 2px +/* + font-size: 105% + font-weight: bold; + text-decoration: underline; + text-align: center; +*/ } From lattner at cs.uiuc.edu Tue Jun 1 13:17:02 2004 From: lattner at cs.uiuc.edu (Chris Lattner) Date: Tue Jun 1 13:17:02 2004 Subject: [llvm-commits] CVS: llvm/docs/CFEBuildInstrs.html Message-ID: <200406011813.NAA17974@zion.cs.uiuc.edu> Changes in directory llvm/docs: CFEBuildInstrs.html updated: 1.16 -> 1.17 --- Log message: * Make it HTML4.01 * Add information about cygwin * Simplify instructions a little and make it more robust (have people just reconfig and build after buildint the CFE) * Remove some obsolete stuff --- Diffs of the changes: (+42 -22) Index: llvm/docs/CFEBuildInstrs.html diff -u llvm/docs/CFEBuildInstrs.html:1.16 llvm/docs/CFEBuildInstrs.html:1.17 --- llvm/docs/CFEBuildInstrs.html:1.16 Sun May 23 16:07:26 2004 +++ llvm/docs/CFEBuildInstrs.html Tue Jun 1 13:13:05 2004 @@ -14,12 +14,17 @@

    1. A Cautionary Note -
    2. Instructions -
    3. License Information + +
    4. +
    5. Instructions
    6. +
    7. License Information
    -

    Written by Brian R. Gaeke

    +

    Written by Brian R. Gaeke and + Chris Lattner

    @@ -46,6 +51,23 @@

    We welcome patches to help make this process simpler.

    + + + + +
    +

    If you are building LLVM and the C front-end under cygwin, please note that +the LLVM and GCC makefiles do not correctly handle spaces in paths. To deal +with this issue, make sure that your LLVM and GCC source and build trees are +located in a top-level directory (like /cygdrive/c/llvm and +/cygdrive/c/llvm-cfrontend), not in a directory that contains a space +(which includes your "home directory", because it lives under the "Documents +and Settings" directory). We welcome patches to fix this issue. +

    +
    +
    Instructions @@ -59,12 +81,11 @@
      % cd llvm
      % ./configure [options...]
    - % gmake tools-only
    + % gmake 
     
    -

    The use of the non-default target "tools-only" means that the - LLVM tools and libraries will build, and the binaries will be - deposited in llvm/tools/Debug, but the runtime (bytecode) - libraries will not build.

    +

    This will build all of the LLVM tools and libraries, but you will see + warnings about missing the C front-end (certain runtime libraries can't + be built without it). Ignore these warnings for now.

  • Add the directory containing the tools to your PATH.

    @@ -73,9 +94,6 @@
     
     
  • Unpack the C/C++ front-end source into cfrontend/src.

  • -
  • Edit src/configure. Change the first line (starting w/ #!) to - contain the correct full pathname of sh.

  • -
  • Make "build" and "install" directories as siblings of the "src" tree.

    @@ -86,12 +104,13 @@
      % set CFEINSTALL = `pwd`/install
     
  • +
  • Configure, build, and install the C front-end:

    -Linux/x86: -
    -MacOS X/PowerPC: +Linux/x86:
    +MacOS X/PowerPC:
    +cygwin/x86:

    @@ -170,11 +189,9 @@
      
     
  • -
  • Go back into the LLVM source tree proper. Edit Makefile.config -to redefine LLVMGCCDIR to the full pathname of the -$CFEINSTALL directory, which is the directory you just -installed the C front-end into. (The ./configure script is likely to -have set this to a directory which does not exist on your system.)

  • +
  • Go back into the LLVM source tree proper. Rerun configure, using +the --with-llvmgccdir=$CFEINSTALL option to specify the path +to the newly built C front-end.

  • If you edited header files during the C/C++ front-end build as described in "Fix 1" above, you must now copy those header files from @@ -184,9 +201,12 @@ libgcc.a library, which you can find by running $CFEINSTALL/bin/gcc --print-libgcc-file-name.)

  • -
  • Build and install the runtime (bytecode) libraries by running:

    +
  • Rebuild your CVS tree. This shouldn't cause the whole thing to be + rebuilt, but it should build the runtime libraries. After the tree is + built, install the runtime libraries into your C front-end build tree. + These are the commands you need.

    - % gmake -C runtime
    + % gmake
      % mkdir $CFEINSTALL/bytecode-libs
      % gmake -C runtime install-bytecode
      % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/bytecode-libs
    @@ -274,7 +294,7 @@
     
       Brian Gaeke
    LLVM Compiler Infrastructure
    - Last modified: $Date: 2004/05/23 21:07:26 $ + Last modified: $Date: 2004/06/01 18:13:05 $ From brukman at cs.uiuc.edu Tue Jun 1 13:24:05 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:24:05 2004 Subject: [llvm-commits] CVS: llvm/docs/doxygen.css Message-ID: <200406011819.NAA25945@zion.cs.uiuc.edu> Changes in directory llvm/docs: doxygen.css updated: 1.2 -> 1.3 --- Log message: * Use sans-serif fonts just like in the rest of doxygen * Reference the lines image correctly * Set font size to make the title stand out --- Diffs of the changes: (+3 -8) Index: llvm/docs/doxygen.css diff -u llvm/docs/doxygen.css:1.2 llvm/docs/doxygen.css:1.3 --- llvm/docs/doxygen.css:1.2 Tue Jun 1 13:09:32 2004 +++ llvm/docs/doxygen.css Tue Jun 1 13:19:28 2004 @@ -77,8 +77,9 @@ vertical-align: middle; } .title { - color: black; background: url("img/lines.gif"); - font-family: "Georgia,Palatino,Times,Roman"; font-weight: bold; + font-size: 25pt; + color: black; background: url("../img/lines.gif"); + font-weight: bold; border-width: 1px; border-style: solid none solid none; text-align: center; @@ -86,10 +87,4 @@ padding-left: 8pt; padding-top: 1px; padding-bottom: 2px -/* - font-size: 105% - font-weight: bold; - text-decoration: underline; - text-align: center; -*/ } From lattner at cs.uiuc.edu Tue Jun 1 13:27:02 2004 From: lattner at cs.uiuc.edu (Chris Lattner) Date: Tue Jun 1 13:27:02 2004 Subject: [llvm-commits] CVS: llvm/docs/ReleaseNotes.html Message-ID: <200406011822.NAA30414@zion.cs.uiuc.edu> Changes in directory llvm/docs: ReleaseNotes.html updated: 1.187 -> 1.188 --- Log message: Fix wandering , add note about cygwin being supported. --- Diffs of the changes: (+20 -7) Index: llvm/docs/ReleaseNotes.html diff -u llvm/docs/ReleaseNotes.html:1.187 llvm/docs/ReleaseNotes.html:1.188 --- llvm/docs/ReleaseNotes.html:1.187 Mon May 24 00:34:32 2004 +++ llvm/docs/ReleaseNotes.html Tue Jun 1 13:22:41 2004 @@ -106,7 +106,7 @@
  • The induction variable substitution pass performs linear function test replacement and exit value replacement optimizations.
  • The LLVM Bytecode file format is now - documented.
  • + documented.
  • LLVM now has first-class support for Accurate Garbage Collection, enabling the use of aggressive copying and generational collectors.
  • @@ -114,6 +114,8 @@ analysis algorithm.
  • Bugpoint can extract individual basic blocks to track down reduce miscompilation testcases.
  • +
  • LLVM and the C front-end now work under Win32 using the cygnus libraries. +This includes the JIT compiler.
  • @@ -262,11 +264,17 @@
    -

    LLVM has been extensively tested on Intel and AMD machines running Red Hat -Linux. It has also been tested under FreeBSD, and on Sun UltraSPARC -workstations running Solaris 8. Additionally, LLVM works on Mac OS X 10.3 and -above, but only with the C backend and interpreter; no native machine-code -generator for the PowerPC is available yet.

    +

    LLVM is known to work in the following platforms:

    + +
      +
    • Intel and AMD machines running Red Hat Linux and FreeBSD (and probably + other unix-like systems).
    • +
    • Sun UltraSPARC workstations running Solaris 8.
    • +
    • PowerPC-based Mac OS X boxes, running 10.3 and above (C backend and + interpreter only, no native codegen is available yet).
    • +
    • Intel and AMD machines running on Win32 with the Cygwin libraries.
    • +
    +

    The core LLVM infrastructure uses GNU autoconf to adapt itself @@ -274,6 +282,11 @@ porting may be required to get LLVM to work on new platforms. We welcome your portability patches and reports of successful builds or error messages.

    +

    Note that the LLVM build system does not currently support directories with +spaces on them when running on Win32/cygwin. We strongly recommend running +LLVM and the C frontend out of a top-level directory without spaces (e.g., +/cygdrive/c/llvm).

    +
    @@ -677,7 +690,7 @@ src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /> The LLVM Compiler Infrastructure
    - Last modified: $Date: 2004/05/24 05:34:32 $ + Last modified: $Date: 2004/06/01 18:22:41 $ From brukman at cs.uiuc.edu Tue Jun 1 13:39:04 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:39:04 2004 Subject: [llvm-commits] CVS: llvm-www/Features.html Message-ID: <200406011835.NAA04787@zion.cs.uiuc.edu> Changes in directory llvm-www: Features.html updated: 1.6 -> 1.7 --- Log message: * Moved "Strengths" sub-section here from the main page * Tightened up whitespace in HTML code --- Diffs of the changes: (+91 -75) Index: llvm-www/Features.html diff -u llvm-www/Features.html:1.6 llvm-www/Features.html:1.7 --- llvm-www/Features.html:1.6 Mon Mar 8 23:44:19 2004 +++ llvm-www/Features.html Tue Jun 1 13:34:58 2004 @@ -1,91 +1,107 @@
    LLVM Features
    -

    -The public release of LLVM is a fully functional -release of our compiler system for C and C++. As such, it includes the -following: -

    +

    The public release of LLVM is a fully functional +release of our compiler system for C and C++. As such, it includes the +following:

      -
    • - Front-ends for C and C++ based on the GCC 3.4 parser. They support the full - ANSI-standard C and C++ languages, plus many GCC extensions. LLVM - also includes a front-end for "Stacker", a - Forth-like language. -
    • - -
    • - A wide range of global scalar optimizations. -
    • +
    • Front-ends for C and C++ based on the GCC 3.4 parser. They support the + full ANSI-standard C and C++ languages, plus many GCC extensions. LLVM also + includes a front-end for "Stacker", a + Forth-like language.
    • + +
    • A wide range of global scalar optimizations.
    • -
    • - A link-time interprocedural optimization framework with a rich set of +
    • A link-time interprocedural optimization framework with a rich set of analyses and transformations, including sophisticated whole-program pointer - analysis, call graph construction, and support for profile-guided - optimizations. -
    • - -
    • - Native code generators for x86 and Sparc. -
    • - -
    • - A Just-In-Time (JIT) code generation system for x86 and Sparc. -
    • - -
    • - A C back-end useful for testing, for supporting targets other than X86 and - Sparc, and allowing LLVM to use a native code generator. -
    • - -
    • - A profiling system similar to gprof. -
    • - -
    • - A test framework with a number of benchmark codes and applications. -
    • - -
    • - APIs and debugging tools to simplify rapid development of LLVM components. -
    • + analysis, call graph construction, and support for profile-guided + optimizations. + +
    • Native code generators for x86 and Sparc.
    • + +
    • A Just-In-Time (JIT) code generation system for x86 and Sparc.
    • + +
    • A C back-end useful for testing, for supporting targets other than X86 + and Sparc, and allowing LLVM to use a native code generator.
    • + +
    • A profiling system similar to gprof.
    • + +
    • A test framework with a number of benchmark codes and applications.
    • + +
    • APIs and debugging tools to simplify rapid development of LLVM + components.
    +
    Strengths of the LLVM System
    + +
    + +
      +
    1. LLVM uses a simple low-level language with + strictly defined semantics.
    2. + +
    3. It includes front-ends for C, + C++, and Stacker (a forth-like language). Front-ends for + Java, Microsoft CLI, and O-Caml are in early development.
    4. + +
    5. It includes an aggressive optimizer, including scalar, interprocedural, + profile-driven, and some simple loop optimizations.
    6. + +
    7. It supports a life-long + compilation model, including link-time, install-time, run-time, and + offline optimization.
    8. + +
    9. LLVM has full support for accurate + garbage collection.
    10. + +
    11. It includes native code generators for X86 and Sparc (both of which work + as JIT or static compilers). LLVM can also compile to C code, for + portability. Other native backends are in development.
    12. + +
    13. LLVM has extensive documentation and has + hosted many projects of various sorts.
    14. + +
    15. Many third-party users have claimed that LLVM is easy to work with and + develop for. For example, the Stacker front-end was written in 4 days by someone who started + knowing nothing about LLVM. Additionally, LLVM has tools to make development easier.
    16. + +
    17. LLVM is under active development and is constantly being extended, + enhanced and improved. See the status updates on the left bar to see the rate + of development.
    18. + +
    19. LLVM is freely available under an OSI-approved "three-clause BSD" license.
    20. +
    + +
    +
    LLVM Audience
    -

    -LLVM can be used in many different kinds of projects. You might be interested -in LLVM if you are: -

    +

    LLVM can be used in many different kinds of projects. You might be +interested in LLVM if you are:

      -
    • - A compiler researcher interested in compile-time, link-time - (interprocedural), and runtime transformations for C and C++ programs. -
    • - -
    • - A virtual machine researcher/developer interested in a portable, - language-independent instruction set and compilation framework. -
    • - -
    • - An architecture researcher interested in compiler/hardware techniques. -
    • - -
    • - A security researcher interested in static analysis or instrumentation. -
    • - -
    • - An instructor (or other person) interested in a system for quick - prototyping of compiler transformations. -
    • - -
    • - An end-user who wants to get better performance out of your code. -
    • +
    • A compiler researcher interested in compile-time, link-time + (interprocedural), and runtime transformations for C and C++ programs.
    • + +
    • A virtual machine researcher/developer interested in a portable, + language-independent instruction set and compilation framework.
    • + +
    • An architecture researcher interested in compiler/hardware + techniques.
    • + +
    • A security researcher interested in static analysis or + instrumentation.
    • + +
    • An instructor or developer interested in a system for quick prototyping of + compiler transformations.
    • + +
    • An end-user who wants to get better performance out of your code.
    Want to Know More?
    From lattner at cs.uiuc.edu Tue Jun 1 13:40:01 2004 From: lattner at cs.uiuc.edu (Chris Lattner) Date: Tue Jun 1 13:40:01 2004 Subject: [llvm-commits] CVS: llvm/docs/CodeGenerator.html Message-ID: <200406011835.NAA07106@zion.cs.uiuc.edu> Changes in directory llvm/docs: CodeGenerator.html updated: 1.2 -> 1.3 --- Log message: Finish the thought that got interrupted when my train arrived. :) --- Diffs of the changes: (+4 -3) Index: llvm/docs/CodeGenerator.html diff -u llvm/docs/CodeGenerator.html:1.2 llvm/docs/CodeGenerator.html:1.3 --- llvm/docs/CodeGenerator.html:1.2 Tue Jun 1 12:18:11 2004 +++ llvm/docs/CodeGenerator.html Tue Jun 1 13:35:00 2004 @@ -203,12 +203,13 @@
    -

    The target description classes require a detailed descriptions of the target +

    The target description classes require a detailed description of the target architecture. These target descriptions often have a large amount of common information (e.g., an add instruction is almost identical to a sub instruction). In order to allow the maximum amount of commonality to be factored out, the LLVM code generator uses the TableGen tool to -allow +describe big chunks of the target machine, which allows the use of domain- and +target-specific abstractions to reduce the amount of repetition.

    @@ -344,7 +345,7 @@ Chris Lattner
    The LLVM Compiler Infrastructure
    - Last modified: $Date: 2004/06/01 17:18:11 $ + Last modified: $Date: 2004/06/01 18:35:00 $ From brukman at cs.uiuc.edu Tue Jun 1 13:40:04 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:40:04 2004 Subject: [llvm-commits] CVS: llvm-www/www-index.html Message-ID: <200406011836.NAA17825@zion.cs.uiuc.edu> Changes in directory llvm-www: www-index.html updated: 1.103 -> 1.104 --- Log message: Moved "Strenghts" section to the Features page. --- Diffs of the changes: (+0 -46) Index: llvm-www/www-index.html diff -u llvm-www/www-index.html:1.103 llvm-www/www-index.html:1.104 --- llvm-www/www-index.html:1.103 Tue Jun 1 12:39:07 2004 +++ llvm-www/www-index.html Tue Jun 1 13:36:00 2004 @@ -69,52 +69,6 @@ -
    Strengths of the LLVM System
    - -
    - -
      -
    1. LLVM uses a simple low-level language with strictly defined semantics.
    2. - -
    3. It includes front-ends for C, - C++, and Stacker (a forth-like language). Front-ends for - Java, Microsoft CLI, and O-Caml are in early development.
    4. - -
    5. It includes an aggressive optimizer, including scalar, interprocedural, - profile-driven, and some simple loop optimizations.
    6. - -
    7. It supports a life-long - compilation model, including link-time, install-time, run-time, and - offline optimization.
    8. - -
    9. LLVM has full support for accurate - garbage collection.
    10. - -
    11. It includes native code generators for X86 and Sparc (both of which work - as JIT or static compilers). LLVM can also compile to C code, for - portability. Other native backends are in development.
    12. - -
    13. LLVM has extensive documentation and has - hosted many projects of various sorts.
    14. - -
    15. Many third-party users have claimed that LLVM is easy to work with and - develop for. For example, the Stacker front-end was written in 4 days by someone who started - knowing nothing about LLVM. Additionally, LLVM has tools to make development easier.
    16. - -
    17. LLVM is under active development and is constantly being extended, - enhanced and improved. See the status updates on the left bar to see the rate - of development.
    18. - -
    19. LLVM is freely available under an OSI-approved "three-clause BSD" license.
    20. -
    - -
    -
    Want to learn more?

    If you'd like to learn more about LLVM, please take a look at the extensive From brukman at cs.uiuc.edu Tue Jun 1 13:44:03 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:44:03 2004 Subject: [llvm-commits] CVS: llvm-www/pubs/2003-09-30-LifelongOptimizationTR.html Message-ID: <200406011839.NAA29858@zion.cs.uiuc.edu> Changes in directory llvm-www/pubs: 2003-09-30-LifelongOptimizationTR.html updated: 1.5 -> 1.6 --- Log message: Fix spelling of `superseded'. --- Diffs of the changes: (+2 -1) Index: llvm-www/pubs/2003-09-30-LifelongOptimizationTR.html diff -u llvm-www/pubs/2003-09-30-LifelongOptimizationTR.html:1.5 llvm-www/pubs/2003-09-30-LifelongOptimizationTR.html:1.6 --- llvm-www/pubs/2003-09-30-LifelongOptimizationTR.html:1.5 Fri Jan 30 19:42:20 2004 +++ llvm-www/pubs/2003-09-30-LifelongOptimizationTR.html Tue Jun 1 13:39:21 2004 @@ -50,7 +50,8 @@

    This paper is an early version of the paper published in CGO'04, and is superceded by it.

    + href="2004-01-30-CGO-LLVM.html">paper published in CGO'04, and is + superseded by it.

    Download:

      From brukman at cs.uiuc.edu Tue Jun 1 13:55:02 2004 From: brukman at cs.uiuc.edu (Misha Brukman) Date: Tue Jun 1 13:55:02 2004 Subject: [llvm-commits] CVS: llvm/docs/FAQ.html Message-ID: <200406011851.NAA09034@zion.cs.uiuc.edu> Changes in directory llvm/docs: FAQ.html updated: 1.22 -> 1.23 --- Log message: * Standardize footer * HTML 4.01 (Strict) compliance --- Diffs of the changes: (+11 -8) Index: llvm/docs/FAQ.html diff -u llvm/docs/FAQ.html:1.22 llvm/docs/FAQ.html:1.23 --- llvm/docs/FAQ.html:1.22 Sun May 23 16:07:26 2004 +++ llvm/docs/FAQ.html Tue Jun 1 13:51:03 2004 @@ -3,7 +3,7 @@ LLVM: Frequently Asked Questions -