From: Sean Silva Date: Wed, 19 Feb 2014 00:12:34 +0000 (+0000) Subject: [docs] Clean up some more llvm-gcc stuff X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=7a8ca279cde02a44bf8c77e20eac1bd5bdbf582b;p=oota-llvm.git [docs] Clean up some more llvm-gcc stuff Some references to llvm-gcc were so crusty that I wasn't sure how to proceed and so I've left them intact. I also slipped in a quick peephole fix to use a :doc: link instead of raw HTML link. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@201619 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/CommandGuide/llc.rst b/docs/CommandGuide/llc.rst index 02ad798c8b6..dddcbaed8f5 100644 --- a/docs/CommandGuide/llc.rst +++ b/docs/CommandGuide/llc.rst @@ -45,7 +45,7 @@ End-user Options Generate code at different optimization levels. These correspond to the ``-O0``, ``-O1``, ``-O2``, and ``-O3`` optimization levels used by - :program:`llvm-gcc` and :program:`clang`. + :program:`clang`. .. option:: -mtriple= diff --git a/docs/CommandGuide/opt.rst b/docs/CommandGuide/opt.rst index 179c297c220..3fed6845550 100644 --- a/docs/CommandGuide/opt.rst +++ b/docs/CommandGuide/opt.rst @@ -65,9 +65,8 @@ OPTIONS .. option:: -std-compile-opts This is short hand for a standard list of *compile time optimization* passes. - This is typically used to optimize the output from the llvm-gcc front end. It - might be useful for other front end compilers as well. To discover the full - set of options available, use the following command: + It might be useful for other front end compilers as well. To discover the + full set of options available, use the following command: .. code-block:: sh diff --git a/docs/DeveloperPolicy.rst b/docs/DeveloperPolicy.rst index 4ebf0f7dd91..b9ac57629e3 100644 --- a/docs/DeveloperPolicy.rst +++ b/docs/DeveloperPolicy.rst @@ -212,13 +212,10 @@ features added. Some tips for getting your testcase approved: directory. The appropriate sub-directory should be selected (see the :doc:`Testing Guide ` for details). -* Test cases should be written in `LLVM assembly language `_ - unless the feature or regression being tested requires another language - (e.g. the 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 should be written in :doc:`LLVM assembly language `. * Test cases, especially for regressions, should be reduced as much as possible, - by `bugpoint `_ or manually. It is unacceptable to place an + by :doc:`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. @@ -517,12 +514,12 @@ to move code from (e.g.) libc++ to the LLVM core without concern, but that code cannot be moved from the LLVM core to libc++ without the copyright owner's permission. -Note that the LLVM Project does distribute llvm-gcc and dragonegg, **which are -GPL.** This means that anything "linked" into llvm-gcc must itself be compatible +Note that the LLVM Project does distribute dragonegg, **which is +GPL.** This means that anything "linked" into dragonegg must itself be compatible with the GPL, and must be releasable under the terms of the GPL. This implies -that **any code linked into llvm-gcc and distributed to others may be subject to +that **any code linked into dragonegg and distributed to others may be subject to the viral aspects of the GPL** (for example, a proprietary code generator linked -into llvm-gcc must be made available under the GPL). This is not a problem for +into dragonegg must be made available under the GPL). This is not a problem for code already distributed under a more liberal license (like the UIUC license), and GPL-containing subprojects are kept in separate SVN repositories whose LICENSE.txt files specifically indicate that they contain GPL code. diff --git a/docs/GetElementPtr.rst b/docs/GetElementPtr.rst index 306a2a87eff..91025d883f2 100644 --- a/docs/GetElementPtr.rst +++ b/docs/GetElementPtr.rst @@ -77,7 +77,7 @@ therefore be indexed and requires an index operand. Consider this example: ... munge(Array); -In this "C" example, the front end compiler (llvm-gcc) will generate three GEP +In this "C" example, the front end compiler (Clang) will generate three GEP instructions for the three indices through "P" in the assignment statement. The function argument ``P`` will be the first operand of each of these GEP instructions. The second operand indexes through that pointer. The third diff --git a/docs/tutorial/LangImpl7.rst b/docs/tutorial/LangImpl7.rst index a2e47b5f8a2..849ce50060c 100644 --- a/docs/tutorial/LangImpl7.rst +++ b/docs/tutorial/LangImpl7.rst @@ -237,7 +237,7 @@ strongly recommend that you use this technique for building SSA form, unless there is an extremely good reason not to. Using this technique is: -- Proven and well tested: llvm-gcc and clang both use this technique +- Proven and well tested: clang uses this technique for local mutable variables. As such, the most common clients of LLVM are using this to handle a bulk of their variables. You can be sure that bugs are found fast and fixed early. diff --git a/docs/tutorial/LangImpl8.rst b/docs/tutorial/LangImpl8.rst index 3534b2e0c93..6f694931ef8 100644 --- a/docs/tutorial/LangImpl8.rst +++ b/docs/tutorial/LangImpl8.rst @@ -72,7 +72,7 @@ For example, try adding: info <../SourceLevelDebugging.html>`_ which is understood by common debuggers like GDB. Adding support for debug info is fairly straightforward. The best way to understand it is to compile some - C/C++ code with "``llvm-gcc -g -O0``" and taking a look at what it + C/C++ code with "``clang -g -O0``" and taking a look at what it produces. - **exception handling support** - LLVM supports generation of `zero cost exceptions <../ExceptionHandling.html>`_ which interoperate with diff --git a/docs/tutorial/OCamlLangImpl7.rst b/docs/tutorial/OCamlLangImpl7.rst index cfb49312c50..98ea93f42f3 100644 --- a/docs/tutorial/OCamlLangImpl7.rst +++ b/docs/tutorial/OCamlLangImpl7.rst @@ -237,7 +237,7 @@ strongly recommend that you use this technique for building SSA form, unless there is an extremely good reason not to. Using this technique is: -- Proven and well tested: llvm-gcc and clang both use this technique +- Proven and well tested: clang uses this technique for local mutable variables. As such, the most common clients of LLVM are using this to handle a bulk of their variables. You can be sure that bugs are found fast and fixed early. diff --git a/docs/tutorial/OCamlLangImpl8.rst b/docs/tutorial/OCamlLangImpl8.rst index 3534b2e0c93..6f694931ef8 100644 --- a/docs/tutorial/OCamlLangImpl8.rst +++ b/docs/tutorial/OCamlLangImpl8.rst @@ -72,7 +72,7 @@ For example, try adding: info <../SourceLevelDebugging.html>`_ which is understood by common debuggers like GDB. Adding support for debug info is fairly straightforward. The best way to understand it is to compile some - C/C++ code with "``llvm-gcc -g -O0``" and taking a look at what it + C/C++ code with "``clang -g -O0``" and taking a look at what it produces. - **exception handling support** - LLVM supports generation of `zero cost exceptions <../ExceptionHandling.html>`_ which interoperate with