| /openbsd/src/gnu/usr.bin/perl/cpan/podlators/t/data/snippets/text/ |
| D | iso-8859-1-error-die | 13 This character cannot be represented in ISO-8859-1, so should produce an
20 This character cannot be represented in ISO-8859-1, so should produce an
|
| D | iso-8859-1-error-pod | 12 This character cannot be represented in ISO-8859-1, so should produce an
19 This character cannot be represented in ISO-8859-1, so should produce an
|
| /openbsd/src/gnu/usr.bin/perl/cpan/podlators/t/data/snippets/man/ |
| D | iso-8859-1-error-die | 13 This character cannot be represented in ISO-8859-1, so should produce an
21 This character cannot be represented in ISO\-8859\-1, so should produce an
|
| D | iso-8859-1-error-pod | 12 This character cannot be represented in ISO-8859-1, so should produce an
20 This character cannot be represented in ISO\-8859\-1, so should produce an
|
| /openbsd/src/gnu/gcc/gcc/config/rs6000/ |
| D | darwin-ldouble-format | 10 represented as (1.0, +0.0) or (1.0, -0.0), and the low part of a NaN
33 Each NaN, quiet or signalling, that can be represented as a 'double'
34 can be represented as a 'long double'. In fact, there are 2^64
|
| /openbsd/src/gnu/usr.bin/binutils/gdb/ |
| D | charset.c | 523 static char represented[] = "\a\b\f\n\r\t\v"; variable
539 ix = strchr (represented, host_char); in default_c_target_char_has_backslash_escape()
541 return backslashed[ix - represented]; in default_c_target_char_has_backslash_escape()
559 return host_char_to_target (represented[ix - backslashable], in default_c_parse_backslash()
|
| /openbsd/src/gnu/usr.bin/perl/t/lib/croak/ |
| D | toke_l1 | 21 …8 sequence that starts with "\xc1" is overlong which can and should be represented with a differen…
|
| /openbsd/src/gnu/llvm/clang/include/clang/Basic/ |
| D | DiagnosticCommonKinds.td | 221 "integer literal is too large to be represented in any %select{signed |}0"
224 "integer literal is too large to be represented in a signed integer type, "
228 "integer literal is too large to be represented in type 'long', "
233 "integer literal is too large to be represented in type 'long', "
238 "integer literal is too large to be represented in type 'long' and is "
|
| /openbsd/src/gnu/usr.bin/gcc/gcc/doc/ |
| D | c-tree.texi | 199 The string represented by the identifier, represented as a
239 Two common container data structures can be represented directly with
363 The number of bits required to represent the type, represented as an
368 The alignment of the type, in bits, represented as an @code{int}.
435 the representation, represented as an @code{unsigned int}. (Note that
444 integer that may be represented by this type. Similarly, the
446 that may be represented by this type.
559 pointer-to-data-member is represented by a @code{POINTER_TYPE} whose
577 represented.
632 A namespace is represented by a @code{NAMESPACE_DECL} node.
[all …]
|
| D | rtl.texi | 64 A string is a sequence of characters. In core it is represented as a
67 a machine description, it is represented in core as a null pointer rather
137 which are represented by single characters. You can determine the class
737 In an RTL dump, this flag is represented as @samp{/c}.
754 In an RTL dump, this flag is represented as @samp{/f}.
790 In an RTL dump, this flag is represented as @samp{/s}.
806 In an RTL dump, this flag is represented as @samp{/i}.
818 In an RTL dump, this flag is represented as @samp{/j}.
838 In an RTL dump, this flag is represented as @samp{/u}.
874 In an RTL dump, this flag is represented as @samp{/v}.
[all …]
|
| /openbsd/src/gnu/gcc/gcc/config/arm/ |
| D | arm-cores.def | 26 The CORE_NAME is the name of the core, represented as a string constant.
27 The CORE_IDENT is the name of the core, represented as an identifier.
|
| /openbsd/src/gnu/gcc/gcc/ |
| D | c-common.def | 30 for the anonymous object represented by the COMPOUND_LITERAL;
|
| /openbsd/src/gnu/gcc/gcc/doc/ |
| D | c-tree.texi | 199 The string represented by the identifier, represented as a
239 Two common container data structures can be represented directly with
363 The number of bits required to represent the type, represented as an
368 The alignment of the type, in bits, represented as an @code{int}.
434 the representation, represented as an @code{unsigned int}. (Note that
443 integer that may be represented by this type. Similarly, the
445 that may be represented by this type.
574 represented.
629 A namespace is represented by a @code{NAMESPACE_DECL} node.
709 A class type is represented by either a @code{RECORD_TYPE} or a
[all …]
|
| D | cfg.texi | 39 point and only one exit. In GCC, basic blocks are represented using
100 In addition to notes, the jump table vectors are also represented as
144 a predecessor of B, and B is a successor of A@. Edges are represented
359 return instructions that are represented by edges with no flags set.
401 within a function. It is represented as an integer scaled in the
413 available. This value is represented as the host's widest integer
432 The basic block frequencies are not represented in the instruction
434 represented for conditional jumps (via the @code{REG_BR_PROB}
441 directly represented, but it may be easily computed from frequencies
|
| D | rtl.texi | 66 A string is a sequence of characters. In core it is represented as a
69 a machine description, it is represented in core as a null pointer rather
139 which are represented by single characters. You can determine the class
878 In an RTL dump, this flag is represented as @samp{/c}.
895 In an RTL dump, this flag is represented as @samp{/f}.
931 In an RTL dump, this flag is represented as @samp{/s}.
947 In an RTL dump, this flag is represented as @samp{/i}.
959 In an RTL dump, this flag is represented as @samp{/j}.
979 In an RTL dump, this flag is represented as @samp{/u}.
1015 In an RTL dump, this flag is represented as @samp{/v}.
[all …]
|
| D | loop.texi | 61 tree. This tree is represented by the @code{struct loops} structure.
63 function. Each of the loops is represented in a @code{struct loop}
82 argument of this function is a set of flags represented in an integer
499 have base objects). Pointer accesses are represented as a one-dimensional
521 If both @code{a} and @code{b} are represented as arrays, compare
525 Else if both @code{a} and @code{b} are represented as pointers, compare
529 However, if @code{a} and @code{b} are represented differently, only try
552 represented by a classical distance vector,
|
| /openbsd/src/gnu/usr.bin/perl/pod/ |
| D | perlnumber.pod | 40 0.9 cannot be represented by a native float, since the binary fraction
47 is represented as a floating point number. On typical hardware, floating
96 If the source number can be represented in the target form, that
|
| /openbsd/src/usr.bin/ssh/ |
| D | PROTOCOL.key | 28 are concatenated and represented as a string.
|
| /openbsd/src/gnu/llvm/llvm/docs/ |
| D | MIRLangRef.rst | 223 The machine basic blocks and their instructions are represented using a custom,
454 The null registers are represented using an underscore ('``_``'). They can also be
455 represented using a '``$noreg``' named register, although the former syntax
659 The named global values are represented using an identifier with the '@' prefix.
663 The unnamed global values are represented using an unsigned numeric value with
700 where ``<kind>`` is describing how the jump table is represented and emitted (plain address, reloca…
717 An external symbol operand is represented using an identifier with the ``&``
848 represented by an empty ``DebugLoc`` object in the machine instruction.
|
| D | JITLink.rst | 202 Absolute and external symbols are represented using plain ``Addressable``
203 instances. Content defined inside the object file is represented using the
215 * ``Content`` is represented as an ``llvm::StringRef``, and accessible via
221 * ``Section`` is represented as a ``Section&`` reference, and accessible via
225 * ``Size`` is represented as a ``size_t``, and is accessible via the
228 * ``Alignment`` is represented as a ``uint64_t``, and available via the
232 * ``AlignmentOffset`` is represented as a ``uint64_t``, and accessible via the
250 * ``Name`` is represented as an ``llvm::StringRef`` (equal to
309 * ``Name`` is represented as an ``llvm::StringRef``, and is accessible via the
312 * ``ProtectionFlags`` are represented as a sys::Memory::ProtectionFlags enum,
[all …]
|
| /openbsd/src/gnu/llvm/llvm/docs/HistoricalNotes/ |
| D | 2001-02-06-TypeNotationDebate.txt | 45 Now with this syntax, his example would be represented as:
|
| D | 2002-05-12-InstListChange.txt | 29 the instructions be represented with a doubly linked list in the
|
| /openbsd/src/gnu/usr.bin/binutils/bfd/doc/ |
| D | mmo.texi | 146 can be represented this way in mmo:
267 with a value represented in one byte.
311 and linked to address @samp{0x4}, is represented by the sequence:
345 represented by:
|
| /openbsd/src/gnu/usr.bin/binutils-2.17/bfd/doc/ |
| D | mmo.texi | 146 can be represented this way in mmo:
267 with a value represented in one byte.
311 and linked to address @samp{0x4}, is represented by the sequence:
345 represented by:
|
| /openbsd/src/gnu/llvm/compiler-rt/lib/builtins/ |
| D | fp_compare_impl.inc | 70 // complement integer representation; if integers are represented in a
|