diff options
| author | Mikhail Glushenkov <foldr@codedgers.com> | 2008-11-25 21:34:29 +0000 |
|---|---|---|
| committer | Mikhail Glushenkov <foldr@codedgers.com> | 2008-11-25 21:34:29 +0000 |
| commit | ebdeca786d127495559dfba80f7e9df5818172d1 (patch) | |
| tree | 3bd0e77314aeb3f62491042bff524594da6bd177 | |
| parent | f80f0aacf9233a11296da6625743a1296560d685 (diff) | |
Small documentation update.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60045 91177308-0d34-0410-b5e6-96231b3b80d8
| -rw-r--r-- | tools/llvmc2/doc/LLVMC-Reference.rst | 6 | ||||
| -rw-r--r-- | tools/llvmc2/doc/LLVMC-Tutorial.rst | 8 |
2 files changed, 8 insertions, 6 deletions
diff --git a/tools/llvmc2/doc/LLVMC-Reference.rst b/tools/llvmc2/doc/LLVMC-Reference.rst index a389ea6968..91f7dda6a8 100644 --- a/tools/llvmc2/doc/LLVMC-Reference.rst +++ b/tools/llvmc2/doc/LLVMC-Reference.rst @@ -41,8 +41,8 @@ language names (which are, in turn, determined from file extensions). If you want to force files ending with ".c" to compile as C++, use the ``-x`` option, just like you would do it with ``gcc``:: - $ llvmc2 -x c hello.cpp - $ # hello.cpp is really a C file + $ # hello.c is really a C++ file + $ llvmc2 -x c++ hello.c $ ./a.out hello @@ -361,7 +361,7 @@ Tool-specific option properties like ``append_cmd`` have (obviously) no meaning in the context of ``OptionList``, so the only properties allowed there are ``help`` and ``required``. -Option lists are used at the file scope. See file +Option lists are used at file scope. See the file ``plugins/Clang/Clang.td`` for an example of ``OptionList`` usage. .. _hooks: diff --git a/tools/llvmc2/doc/LLVMC-Tutorial.rst b/tools/llvmc2/doc/LLVMC-Tutorial.rst index 9c6741eba1..1b54531917 100644 --- a/tools/llvmc2/doc/LLVMC-Tutorial.rst +++ b/tools/llvmc2/doc/LLVMC-Tutorial.rst @@ -23,8 +23,10 @@ much as possible, so most of the familiar options work:: $ ./a.out hello -For further help on command-line LLVMC usage, refer to the ``llvmc ---help`` output. +This will invoke ``llvm-g++`` under the hood (you can see which +commands are executed by using the ``-v`` option). For further help on +command-line LLVMC usage, refer to the ``llvmc --help`` output. + Using LLVMC to generate toolchain drivers ========================================= @@ -51,7 +53,7 @@ reference manual. Contents of the file ``Simple.td`` look like this:: // Include common definitions - include "Common.td" + include "llvm/CompilerDriver/Common.td" // Tool descriptions def gcc : Tool< |