| /toolchain/binutils/binutils-2.25/include/coff/ |
| sparc.h | 143 /********************** RELOCATION DIRECTIVES **********************/
|
| /prebuilts/go/darwin-x86/doc/ |
| asm.html | 77 The <code>FUNCDATA</code> and <code>PCDATA</code> directives contain information
263 Instructions, registers, and assembler directives are always in UPPER CASE to remind you
294 <h3 id="directives">Directives</h3>
297 The assembler uses various directives to bind text and data to symbol names.
335 <code>DATA</code> directives followed by a <code>GLOBL</code> directive.
347 The <code>DATA</code> directives for a given symbol must be written with increasing offsets.
355 The <code>GLOBL</code> directive must follow any corresponding <code>DATA</code> directives.
379 There may be one or two arguments to the directives.
455 even without <code>DATA</code> and <code>GLOBL</code> directives
[all...] |
| /prebuilts/go/linux-x86/doc/ |
| asm.html | 77 The <code>FUNCDATA</code> and <code>PCDATA</code> directives contain information
263 Instructions, registers, and assembler directives are always in UPPER CASE to remind you
294 <h3 id="directives">Directives</h3>
297 The assembler uses various directives to bind text and data to symbol names.
335 <code>DATA</code> directives followed by a <code>GLOBL</code> directive.
347 The <code>DATA</code> directives for a given symbol must be written with increasing offsets.
355 The <code>GLOBL</code> directive must follow any corresponding <code>DATA</code> directives.
379 There may be one or two arguments to the directives.
455 even without <code>DATA</code> and <code>GLOBL</code> directives
[all...] |
| /external/bison/tests/ |
| headers.at | 26 # AT_TEST_CPP_GUARD_H(BASE-NAME, [DIRECTIVES])
127 # AT_TEST([PREFIX], [DIRECTIVES])
|
| /external/clang/include/clang/AST/ |
| DeclContextInternals.h | 203 // Using directives end up in a special entry which contains only
204 // other using directives, so all this logic is wasted for them.
|
| /external/ipsec-tools/src/racoon/doc/ |
| README.plainrsa | 77 remote public key(s), you should use the following directives:
82 Notice the option "plain_rsa" for both directives.
|
| /external/okhttp/okhttp/src/main/java/com/squareup/okhttp/ |
| Request.java | 98 * Returns the cache control directives for this response. This is never null,
212 * any directives, this clears this request's cache-control headers.
|
| /frameworks/base/media/java/android/media/ |
| MediaCodecList.java | 207 * @param format A decoder media format with optional feature directives.
231 * @param format An encoder media format with optional feature directives.
|
| /toolchain/binutils/binutils-2.25/gas/doc/ |
| c-m68k.texi | 20 * M68K-Directives:: 680x0 Machine Directives
402 The floating point formats generated by directives are these.
420 @node M68K-Directives
421 @section 680x0 Machine Directives
423 @cindex M680x0 directives
424 @cindex directives, M680x0
426 understands the following directives.
|
| c-v850.texi | 13 * V850 Directives:: V850 Machine Directives
269 @node V850 Directives
270 @section V850 Machine Directives
272 @cindex machine directives, V850
273 @cindex V850 machine directives
|
| as.texinfo | 6 @c (2) for platform-specific directives, examine md_pseudo_op
8 @c (3) for object-format specific directives, examine obj_pseudo_op
10 @c (4) portable directives in potable[] in read.c
189 * Pseudo Ops:: Assembler Directives
592 omit debugging directives
695 Add directory @var{dir} to the search list for @code{.include} directives.
[all...] |
| c-arm.texi | 22 * ARM Directives:: ARM Machine Directives
526 @node ARM Directives
527 @section ARM Machine Directives
529 @cindex machine directives, ARM
530 @cindex ARM machine directives
541 These directives write 2, 4 or 8 byte values to the output section.
599 @cindex @code{.dn} and @code{.qn} directives, ARM
603 The @code{dn} and @code{qn} directives are used to create typed
609 If these directives are used to create typed aliases, those aliases ca
[all...] |
| c-d30v.texi | 177 directives for each instruction. Just append the directive after the
178 instruction proper. The directives are:
285 directives generates @sc{ieee} floating-point numbers for compatibility
|
| c-pdp11.texi | 18 * PDP-11-Pseudos:: Assembler Directives
288 @section Assembler Directives
291 dependent assembler directives.
|
| /toolchain/binutils/binutils-2.25/gas/testsuite/gas/m68hc11/ |
| malis.s | 125 ;; Section 8.2.12 Assembler Directives
127 ;; Section 8.2.12.1 Conditional Directives
|
| /toolchain/binutils/binutils-2.25/ld/testsuite/ld-d10v/ |
| d10v.exp | 61 # options in the "source" directives. See below.
65 # directives, when using multiple files.
|
| /toolchain/binutils/binutils-2.25/ |
| ylwrap | 101 # We'll later need for a correct munging of "#line" directives.
187 # Munge "#line" or "#" directives. Don't let the resulting
|
| /external/clang/docs/ |
| Modules.rst | 35 * **Fragility**: ``#include`` directives are treated as textual
46 ``#include`` directives or introduce ``#undef`` directives to break
127 The primary user-level feature of modules is the import operation, which provides access to the API of software libraries. However, today's programs make extensive use of ``#include``, and it is unrealistic to assume that all of this code will change overnight. Instead, modules automatically translate ``#include`` directives into the corresponding module import. For example, the include directive
144 different strategy is used for ``#include_next`` directives in such files: the
154 The crucial link between modules and headers is described by a *module map*, which describes how a collection of existing headers maps on to the (logical) structure of a module. For example, one could imagine a module ``std`` covering the C standard library. Each of the C standard library headers (``<stdio.h>``, ``<stdlib.h>``, ``<math.h>``, etc.) would contribute to the ``std`` module, by placing their respective APIs into the corresponding submodule (``std.io``, ``std.lib``, ``std.math``, etc.). Having a list of the headers that are part of the ``std`` module allows the compiler to build the ``std`` module as a standalone entity, and having the mapping from header names to (sub)modules allows the automatic translation of ``#include`` directives to module imports.
242 * A set of macro directives is *consistent* if it consists of only ``#undef`` directives, or if all ``#define`` directives in the set define the macro name to the same sequence of tokens (following the usual rules for macro redefinitions).
243 * If a macro name is used and the set of active directives is not consistent, the program is ill-formed. Otherwise, the (unique) meaning of the macro name is (…)
[all...] |
| /build/kati/ |
| INTERNALS.md | 117 * Make directives
127 In addition to include directive, there are ifeq/ifneq/ifdef/ifndef directives
128 and export/unexport directives. Also, kati internally uses "parse error
149 a statement only for rules. Storing assignments or directives in a variable
150 won't work as assignments or directives. For example
238 * Make directives
240 There is nothing tricky around commands and make directives. A rule statement
|
| /external/webrtc/webrtc/base/ |
| httpclient.cc | 62 HttpAttributeList directives; local
63 HttpParseAttributes(value.data(), value.size(), directives);
64 // Response Directives Summary:
73 if (HttpHasAttribute(directives, "no-store", NULL)) {
75 } else if (HttpHasAttribute(directives, "public", NULL)) {
|
| /ndk/sources/host-tools/make-3.81/ |
| ansi2knr.c | 43 * intervening comments and/or preprocessor directives), except that a line
52 * ignore whitespace, comments, and preprocessor directives, except that
83 lpd 1999-08-17 added code to allow preprocessor directives
376 * Skip forward or backward over one or more preprocessor directives.
410 * Skip over whitespace, comments, and preprocessor directives,
|
| /build/soong/androidmk/parser/ |
| parser.go | 530 var directives = [...]string{ var
583 sort.Strings(directives[:])
588 for _, d := range directives {
|
| /dalvik/opcode-gen/ |
| opcode-gen.awk | 50 # Detect directives.
59 # comment for directives.
65 # Handlers for all of the directives.
|
| /external/clang/include/clang/Lex/ |
| PreprocessingRecord.h | 58 /// \defgroup Preprocessing directives
198 /// \brief The kind of inclusion directives known to the
288 /// including the various preprocessing directives processed, macros
|
| /external/clang/lib/Parse/ |
| ParseOpenMP.cpp | 1 //===--- ParseOpenMP.cpp - OpenMP directives parsing ----------------------===//
10 /// \brief This file implements parsing of all OpenMP directives and clauses.
26 // OpenMP declarative directives.
32 // TODO: add other combined directives in topological order.
84 /// \brief Parsing of declarative OpenMP directives.
152 /// \brief Parsing of declarative or executable OpenMP directives.
[all...] |
