[llvm-commits] [llvm-top] r62222 - in /llvm-top/trunk: ./ README.txt

[Duncan Sands]

Author: baldrick
Date: Wed Jan 14 08:27:20 2009
New Revision: 62222

URL: http://llvm.org/viewvc/llvm-project?rev=62222&view=rev
Log:
Support for llvm-gcc-4.2.

Modified:
    llvm-top/trunk/   (props changed)
    llvm-top/trunk/README.txt

Propchange: llvm-top/trunk/

------------------------------------------------------------------------------
--- svn:ignore (original)
+++ svn:ignore Wed Jan 14 08:27:20 2009
@@ -3,8 +3,10 @@
 .options
 sample
 build.llvm-gcc-4.0
+build.llvm-gcc-4.2
 website
 llvm-gcc-4.0
+llvm-gcc-4.2
 test-suite
 build.llvm
 llvm

Modified: llvm-top/trunk/README.txt
URL: http://llvm.org/viewvc/llvm-project/llvm-top/trunk/README.txt?rev=62222&r1=62221&r2=62222&view=diff

==============================================================================
--- llvm-top/trunk/README.txt (original)
+++ llvm-top/trunk/README.txt Wed Jan 14 08:27:20 2009
@@ -17,13 +17,13 @@
 Once you've checked out llvm-top, you can then check out a module (and all its
 dependencies) with the "get" script located here. For example:
 
-  ./get llvm-gcc-4-0
+  ./get llvm-gcc-4.2
 
-which will check out both llvm and llvm-gcc-4-0 because the latter depends on
+which will check out both llvm and llvm-gcc-4.2 because the latter depends on
 the former.  You can check out any number of modules using the "get" script, 
 for example, like this:
 
-  ./get llvm-gcc-4.0 test-suite stacker
+  ./get llvm-gcc-4.2 test-suite stacker
 
 
 In addition to checking out software, there are several more scripts in 
@@ -119,17 +119,17 @@
 
 So, for example, consider:
 
-  ./build llvm-gcc-4.0 ENABLE_OPTIMIZED=1 PREFIX=/my/install/dir VERBOSE=1
+  ./build llvm-gcc-4.2 ENABLE_OPTIMIZED=1 PREFIX=/my/install/dir VERBOSE=1
 
 As you might guess, this will do the following:
 
-  1. Check out the llvm-gcc-4.0 module
-  2. Check out the core module because llvm-gcc-4.0 depends on core
+  1. Check out the llvm-gcc-4.2 module
+  2. Check out the core module because llvm-gcc-4.2 depends on core
   3. Check out the support module because core depends on support
   4. Build the support module in optimized mode and configure it to install
      into /my/install/dir
   5. Build the core module the same way.
-  6. Build the llvm-gcc-4.0 module the same way.
+  6. Build the llvm-gcc-4.2 module the same way.
   7. Do all of the above with some simple progress messages.
 
 The modules available are:
@@ -138,7 +138,7 @@
   sample       - A sample module you can use as a template for your own
   support      - The support libraries, makefile system, etc.
   core         - The core llvm software (currently "llvm")
-  llvm-gcc-4.0 - The C/C++/Obj-C front end for llvm, based on GCC 4.0
+  llvm-gcc-4.2 - The C/C++/Obj-C front end for llvm, based on GCC 4.2
   llvm-gcc-4.2 - The C/C++/Obj-C front end for llvm, based on GCC 4.2
   cfe          - The new C/C++/Obj-C front end for llvm
   test-suite   - The llvm test suite