From: Chad Rosier Date: Sun, 26 Feb 2012 22:26:37 +0000 (+0000) Subject: Remove more GCC FE build stuff. X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=7497a9a7e816857402cf78ac930f286e800c69cf;p=oota-llvm.git Remove more GCC FE build stuff. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@151507 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html deleted file mode 100644 index ab10844a8e0..00000000000 --- a/docs/CFEBuildInstrs.html +++ /dev/null @@ -1,29 +0,0 @@ - - - - - - Building the LLVM C/C++ Front-End - - - -
-This page has moved here. -
- - - -
-
- Valid CSS - Valid HTML 4.01 - - LLVM Compiler Infrastructure
- Last modified: $Date: 2008-02-13 17:46:10 +0100 (Wed, 13 Feb 2008) $ -
- - - diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 3495f87dc58..4d41208ea5a 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -199,7 +199,7 @@ also be a good place to start.

Consult the Getting Started with LLVM section for detailed information on configuring and compiling LLVM. See Setting Up Your Environment for tips that simplify -working with the GCC front end and LLVM tools. Go to Program +working with the Clang front end and LLVM tools. Go to Program Layout to learn about the layout of the source code tree.

@@ -375,10 +375,6 @@ able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code generation should work as well, although the generated native code may not work on your platform.

-

The GCC front end is not very portable at the moment. If you want to get it -to work on another platform, you can download a copy of the source and try to compile it on your platform.

- @@ -551,8 +547,7 @@ href="http://gcc.gnu.org/PR13392">serious bug which causes it to crash in the "convert_from_eh_region_ranges_1" GCC function.

Cygwin GCC 3.3.3: The version of GCC 3.3.3 commonly shipped with - Cygwin does not work. Please upgrade - to a newer version if possible.

+ Cygwin does not work.

SuSE GCC 3.3.3: The version of GCC 3.3.3 shipped with SuSE 9.1 (and possibly others) does not compile LLVM correctly (it appears that exception handling is broken in some cases). Please download the FSF 3.3.3 or upgrade @@ -664,12 +659,6 @@ All these paths are absolute:

can be the same as SRC_ROOT).

-
LLVMGCCDIR -
- This is where the LLVM GCC Front End is installed. -

- For the pre-built GCC front end binaries, the LLVMGCCDIR is - llvm-gcc/platform/llvm-gcc. @@ -796,10 +785,6 @@ you get it from the Subversion repository:

configured by the LLVM configure script as well as automatically updated when you run svn update.

-

If you would like to get the GCC front end source code, you can also get it -and build it yourself. Please follow these -instructions to successfully get and build the LLVM GCC front-end.

- @@ -1451,7 +1436,7 @@ different tools.

This directory contains libraries which are compiled into LLVM bitcode and -used when linking programs with the GCC front end. Most of these libraries are +used when linking programs with the Clang front end. Most of these libraries are skeleton versions of real libraries; for example, libc is a stripped down version of glibc.

diff --git a/docs/index.html b/docs/index.html index 411be426a77..4d50b4f9d08 100644 --- a/docs/index.html +++ b/docs/index.html @@ -98,8 +98,9 @@ the LLVM system.
  • LLVM Testing Infrastructure Guide - A reference manual for using the LLVM testing infrastructure.
  • -
  • How to build the Ada/C/C++/Fortran front-ends - -Instructions for building gcc front-ends from source.
  • +
  • How to build the C, C++, ObjC, +and ObjC++ front end - Instructions for building the clang front-end from +source.
  • Packaging guide - Advice on packaging LLVM into a distribution.