summaryrefslogtreecommitdiffstats
path: root/llvm/tools
diff options
context:
space:
mode:
authorMikhail Glushenkov <foldr@codedgers.com>2008-11-25 21:34:53 +0000
committerMikhail Glushenkov <foldr@codedgers.com>2008-11-25 21:34:53 +0000
commit86d5fa8f2821298a318d34eacad3f880ed5ef754 (patch)
tree709cdc1a651d5ab6c19617a26be6c8a07265a3f3 /llvm/tools
parenteafa1dd9d9deeae6468cdd92167bd6c33a8159ec (diff)
downloadbcm5719-llvm-86d5fa8f2821298a318d34eacad3f880ed5ef754.tar.gz
bcm5719-llvm-86d5fa8f2821298a318d34eacad3f880ed5ef754.zip
docs: Add author info + fix incorrect code example.
llvm-svn: 60046
Diffstat (limited to 'llvm/tools')
-rw-r--r--llvm/tools/llvmc2/doc/LLVMC-Reference.rst13
-rw-r--r--llvm/tools/llvmc2/doc/LLVMC-Tutorial.rst1
2 files changed, 9 insertions, 5 deletions
diff --git a/llvm/tools/llvmc2/doc/LLVMC-Reference.rst b/llvm/tools/llvmc2/doc/LLVMC-Reference.rst
index 91f7dda6a88..01a8be0d20e 100644
--- a/llvm/tools/llvmc2/doc/LLVMC-Reference.rst
+++ b/llvm/tools/llvmc2/doc/LLVMC-Reference.rst
@@ -1,6 +1,7 @@
===================================
Customizing LLVMC: Reference Manual
===================================
+:Author: Mikhail Glushenkov <foldr@codedegers.com>
LLVMC is a generic compiler driver, designed to be customizable and
extensible. It plays the same role for LLVM as the ``gcc`` program
@@ -193,8 +194,10 @@ The definition of the compilation graph (see file
Edge<"llvm_gcc_cpp", "llc">,
...
- OptionalEdge<"llvm_gcc_c", "opt", [(switch_on "opt")]>,
- OptionalEdge<"llvm_gcc_cpp", "opt", [(switch_on "opt")]>,
+ OptionalEdge<"llvm_gcc_c", "opt", (case (switch_on "opt"),
+ (inc_weight))>,
+ OptionalEdge<"llvm_gcc_cpp", "opt", (case (switch_on "opt"),
+ (inc_weight))>,
...
OptionalEdge<"llvm_gcc_assembler", "llvm_gcc_cpp_linker",
@@ -437,7 +440,7 @@ use TableGen inheritance instead.
* Possible tests are:
- - ``switch_on`` - Returns true if a given command-line option is
+ - ``switch_on`` - Returns true if a given command-line switch is
provided by the user. Example: ``(switch_on "opt")``. Note that
you have to define all possible command-line options separately in
the tool descriptions. See the next section for the discussion of
@@ -481,8 +484,8 @@ Language map
One last thing that you will need to modify when adding support for a
new language to LLVMC is the language map, which defines mappings from
file extensions to language names. It is used to choose the proper
-toolchain(s) for a given input file set. Language map definition is
-located in the file ``Tools.td`` and looks like this::
+toolchain(s) for a given input file set. Language map definition looks
+like this::
def LanguageMap : LanguageMap<
[LangToSuffixes<"c++", ["cc", "cp", "cxx", "cpp", "CPP", "c++", "C"]>,
diff --git a/llvm/tools/llvmc2/doc/LLVMC-Tutorial.rst b/llvm/tools/llvmc2/doc/LLVMC-Tutorial.rst
index 1b545319176..724fd4dfacb 100644
--- a/llvm/tools/llvmc2/doc/LLVMC-Tutorial.rst
+++ b/llvm/tools/llvmc2/doc/LLVMC-Tutorial.rst
@@ -1,6 +1,7 @@
======================
Tutorial - Using LLVMC
======================
+:Author: Mikhail Glushenkov <foldr@codedegers.com>
LLVMC is a generic compiler driver, which plays the same role for LLVM
as the ``gcc`` program does for GCC - the difference being that LLVMC
OpenPOWER on IntegriCloud