[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.

llvm-svn: 201619

4 files changed, 4 insertions, 4 deletions

diff --git a/llvm/docs/tutorial/LangImpl7.rst b/llvm/docs/tutorial/LangImpl7.rst
index a2e47b5f8a2..849ce50060c 100644
--- a/llvm/docs/tutorial/LangImpl7.rst
+++ b/llvm/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/llvm/docs/tutorial/LangImpl8.rst b/llvm/docs/tutorial/LangImpl8.rst
index 3534b2e0c93..6f694931ef8 100644
--- a/llvm/docs/tutorial/LangImpl8.rst
+++ b/llvm/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/llvm/docs/tutorial/OCamlLangImpl7.rst b/llvm/docs/tutorial/OCamlLangImpl7.rst
index cfb49312c50..98ea93f42f3 100644
--- a/llvm/docs/tutorial/OCamlLangImpl7.rst
+++ b/llvm/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/llvm/docs/tutorial/OCamlLangImpl8.rst b/llvm/docs/tutorial/OCamlLangImpl8.rst
index 3534b2e0c93..6f694931ef8 100644
--- a/llvm/docs/tutorial/OCamlLangImpl8.rst
+++ b/llvm/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