Searched +refs:llvm +refs:mode +refs:syntax +refs:table (Results 1 – 8 of 8) sorted by relevance
| /external/llvm/docs/TableGen/ |
| D | index.rst | 31 `Clang diagnostics and attributes <http://clang.llvm.org/docs/UsersManual.html#controlling-errors-a… 34 an emacs "TableGen mode" and a vim language file in the ``llvm/utils/emacs`` and 35 ``llvm/utils/vim`` directories of your LLVM distribution, respectively. 43 TableGen files are interpreted by the TableGen program: `llvm-tblgen` available 51 specifies the file to read. If a filename is not specified, ``llvm-tblgen`` 55 selectable on the command line (type '``llvm-tblgen -help``' for a list). For 62 $ llvm-tblgen X86.td -print-enums -class=Register 72 $ llvm-tblgen X86.td -print-enums -class=Instruction 88 With no other arguments, `llvm-tblgen` parses the specified file and prints out all 93 .. code-block:: llvm [all …]
|
| /external/llvm/docs/ |
| D | GettingStarted.rst | 20 The second piece is the `Clang <http://clang.llvm.org/>`_ front end. This 33 Getting Started <http://clang.llvm.org/get_started.html>`_ page might also be a 43 * ``cd where-you-want-llvm-to-live`` 44 * ``svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm`` 48 * ``cd where-you-want-llvm-to-live`` 49 * ``cd llvm/tools`` 50 * ``svn co http://llvm.org/svn/llvm-project/cfe/trunk clang`` 54 * ``cd where-you-want-llvm-to-live`` 55 * ``cd llvm/projects`` 56 * ``svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt`` [all …]
|
| D | CodeGenerator.rst | 40 These interfaces are defined in ``include/llvm/Target/``. 45 ``include/llvm/CodeGen/``. At this level, concepts like "constant pool 194 The LLVM target description classes (located in the ``include/llvm/Target`` 330 ``include/llvm/CodeGen``). This representation is completely target agnostic, 369 .. code-block:: llvm 382 the ``include/llvm/CodeGen/MachineInstrBuilder.h`` file. The ``BuildMI`` 434 .. code-block:: llvm 444 .. code-block:: llvm 461 .. code-block:: llvm 520 a ``MachineRegisterInfo``. See ``include/llvm/CodeGen/MachineFunction.h`` for [all …]
|
| D | MakefileGuide.rst | 41 ``llvm/projects`` directory. Any directory under ``projects`` that has both a 44 LLVM Makefile System nor even placement in the ``llvm/projects`` 170 documentation <writing-an-llvm-pass-makefile>` has an example of why you might 235 (unreferenced) symbols will not be included when the ``.a`` syntax is used. Note 455 Variables listed in the table below should be set *before* the inclusion of 538 passed to the ``llvm-config`` tool to generate a link line for the 540 specified. The ``llvm-config`` tool will figure out the library dependencies 610 Specifies the directory of tests to run in ``llvm/test``. 708 Specifies the path to the ``llvm-as`` tool. 763 Variables listed in the table below can be used by the user's Makefile but [all …]
|
| D | CommandLine.rst | 86 #include "llvm/Support/CommandLine.h" 101 library uses a declarative syntax to model command line arguments with the 207 terminal, "``--quiet``" to enable quiet mode, and "``-q``" for backwards 325 The answer is that it uses a table-driven generic parser (unless you specify 1112 an explicit '``-foo=true``'. If an option is specified with this mode, it is 1121 value must be provided. This mode informs the command line library that if an 1260 syntax. The program reads these files and inserts the contents into argv, 1295 using namespace llvm; 1618 option using special syntax for a not-very-special data-type. The drawback 1729 library. Examples of this include the ``llvm::DebugFlag`` exported by the [all …]
|
| /external/llvm/include/llvm/Target/ |
| D | Target.td | 16 include "llvm/IR/Intrinsics.td" 110 // is invalid for this mode/flavour. 285 // DwarfRegNum - This class provides a mapping of the llvm register enumeration 295 // is invalid for this mode/flavour. 302 // from dwarf register number to llvm register. 310 include "llvm/Target/TargetSchedule.td" 851 // syntax on X86 for example). 875 // (e.g. AT&T vs Intel syntax on X86 for example). This class can be 955 /// InstAlias - This defines an alternate assembly syntax that is allowed to 976 // Subtargets can have multiple different asmwriters (e.g. AT&T vs Intel syntax [all …]
|
| /external/clang/docs/ |
| D | InternalsManual.rst | 22 `data-structures <http://llvm.org/docs/ProgrammersManual.html>`_, including 257 The parser is very unforgiving. A syntax error, even whitespace, will abort, 365 semicolon at the end of a statement or a use of deprecated syntax that is 444 mode. Instead of formatting and printing out the diagnostics, this 448 documentation for the ``-verify`` mode can be found in the Clang API 539 `LLVM bitstream format <http://llvm.org/docs/BitCodeFormat.html>`_. 599 not reading in "raw" mode) this contains a pointer to the unique hash value 731 * The lexer can operate in "raw" mode. This mode has several features that 734 This mode is used for lexing within an "``#if 0``" block, for example. 736 support the ``-C`` preprocessor mode, which passes comments through, and is [all …]
|
| D | LanguageExtensions.rst | 285 support for ``V.xyzw`` syntax and other tidbits as seen in OpenCL. An example 302 Giving ``-faltivec`` option to clang enables support for AltiVec vector syntax 356 The table below shows the support for each operation by vector extension. A 685 alternate function declaration syntax with trailing return type is enabled. 828 languages supported by Clang. The syntax is the same as that given in the C11 931 The syntax and high level language feature description is in 1132 `static analyzer <http://clang-analyzer.llvm.org>`_ Some exceptions may be 1169 <http://clang-analyzer.llvm.org/annotations.html#cocoa_mem>`_. 1217 This extension also works in C++ mode, as far as that goes, but does not apply 1219 syntax to be used with ``std::complex`` with the same meaning.) [all …]
|