X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FGettingStarted.html;h=0e871336deb83ca2aa1345113c8439ded797076a;hb=1d33bb310865528f5b1a303e33891366457bc0ef;hp=f75fbe2c9274cfcef4e73acff0c6450936d7109f;hpb=c75a04bd2e6fd33438faf6e0aa26fc1261876a0a;p=oota-llvm.git diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index f75fbe2c927..0e871336deb 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -52,6 +52,9 @@
First, LLVM comes in two pieces. The first piece is the LLVM suite. This contains all of the tools, libraries, and header files needed to use the low level virtual machine. It contains an assembler, disassembler, bytecode -analyzer, and bytecode optimizer. It also contains a test suite that can be +analyzer and bytecode optimizer. It also contains a test suite that can be used to test the LLVM tools and the GCC front end.
The second piece is the GCC front end. This component provides a version of GCC that compiles C and C++ code into LLVM bytecode. Currently, the GCC front -end is a modified version of GCC 3.4 (we track the GCC 3.4 development). Once +end uses the GCC parser to convert code to LLVM. Once compiled into LLVM bytecode, a program can be manipulated with the LLVM tools from the LLVM suite.
@@ -115,11 +118,11 @@ and performance.LLVM is known to work on the following platforms:
-OS | Arch | @@ -257,7 +261,7 @@ software you will need.
---|
OS | Arch | @@ -305,17 +309,18 @@ up
---|
Package | Version | Notes |
---|---|---|
Variable | Purpose |
---|---|
CC | @@ -806,14 +820,14 @@ script to configure the build system: dejagnu based test suite in llvm/test. If you don't specify this option, the LLVM configure script will search for the tcl 8.4 and 8.3 releases. - +