6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-15 04:30:12 +00:00
Code Issues Projects Releases Wiki Activity

Small documentation update.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60045 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Mikhail Glushenkov 2008-11-25 21:34:29 +00:00
parent f80f0aacf9
commit ebdeca786d
2 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
tools/llvmc2/doc/LLVMC-Reference.rst
View File

@ -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 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``:: C++, use the ``-x`` option, just like you would do it with ``gcc``::
$ llvmc2 -x c hello.cpp $ # hello.c is really a C++ file
$ # hello.cpp is really a C file $ llvmc2 -x c++ hello.c
$ ./a.out $ ./a.out
hello 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 no meaning in the context of ``OptionList``, so the only properties
allowed there are ``help`` and ``required``. 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. ``plugins/Clang/Clang.td`` for an example of ``OptionList`` usage.
.. _hooks: .. _hooks:

8
tools/llvmc2/doc/LLVMC-Tutorial.rst
View File

@ -23,8 +23,10 @@ much as possible, so most of the familiar options work::
$ ./a.out $ ./a.out
hello hello
For further help on command-line LLVMC usage, refer to the ``llvmc This will invoke ``llvm-g++`` under the hood (you can see which
--help`` output. 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 Using LLVMC to generate toolchain drivers
========================================= =========================================
@ -51,7 +53,7 @@ reference manual.
Contents of the file ``Simple.td`` look like this:: Contents of the file ``Simple.td`` look like this::
// Include common definitions // Include common definitions
include "Common.td" include "llvm/CompilerDriver/Common.td"
// Tool descriptions // Tool descriptions
def gcc : Tool< def gcc : Tool<