| /netbsd-src/external/gpl2/send-pr/dist/send-pr/ |
| H A D | states.texi | 14 @table @dfn
16 @cindex initial state (@dfn{open})
17 @cindex state---@dfn{open}
24 @cindex state---@dfn{analyzed}
32 @cindex state---@dfn{feedback}
39 @cindex state---@dfn{closed}
40 @cindex final state (@dfn{closed})
47 @cindex state---@dfn{suspended}
|
| H A D | send-pr.texi | 91 partially administer a database of @dfn{Problem Reports}, or @dfn{PRs},
95 been @dfn{closed}.
124 A @dfn{Problem Report} is a message that describes a problem you are
128 organized into @dfn{fields} which contain data describing you, your
131 their lifetimes, from @dfn{open} to @dfn{closed} (@pxref{States,,States
446 The bug has gone into @dfn{feedback} status now, until we get the patch,
449 the PR from @dfn{feedback} to @dfn{closed}.
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/doc/ |
| H A D | configterms.texi | 17 are building on (@dfn{build}), the machine that you are building for
18 (@dfn{host}), and the machine that GCC will produce code for
19 (@dfn{target}). When you configure GCC, you specify these with
27 @dfn{native}. If build and host are the same but target is different,
28 this is called a @dfn{cross}. If build, host, and target are all
29 different this is called a @dfn{canadian} (for obscure reasons dealing
33 different system. Some people call this a @dfn{host-x-host},
34 @dfn{crossed native}, or @dfn{cross-built native}. If build and target
38 There is a proposal to call this a @dfn{crossback}.
|
| H A D | standards.texi | 69 This standard, in both its forms, is commonly known as @dfn{C89}, or
70 occasionally as @dfn{C90}, from the dates of ratification.
85 as @dfn{AMD1}; the amended standard is sometimes known as @dfn{C94} or
86 @dfn{C95}. To select this standard in GCC, use the option
91 9899:1999, and is commonly known as @dfn{C99}. (While in
93 @dfn{C9X}.) GCC has substantially
102 A fourth version of the C standard, known as @dfn{C11}, was published
104 standard version were referred to as @dfn{C1X}.)
109 known as @dfn{C17} and is supported with @option{-std=c17} or
114 A further version of the C standard, known as @dfn{C2X}, is under
[all …]
|
| H A D | frontends.texi | 22 The abbreviation @dfn{GCC} has multiple meanings in common use. The
27 of the @dfn{language-independent} component of GCC: code shared among the
59 sort of preprocessor should not be confused with the @dfn{C
|
| H A D | install-old.texi | 44 The @dfn{build} machine is the system which you are using, the
45 @dfn{host} machine is the system where you want to run the resulting
46 compiler (normally the build machine), and the @dfn{target} machine is
57 In those cases, specify the build machine's @dfn{configuration name}
|
| H A D | cfg.texi | 96 instruction (the @dfn{head}) and the last instruction (the @dfn{tail})
97 or @dfn{end} of the instruction stream contained in a basic block. In
111 contains not only the ``real'' instructions, but also @dfn{notes}
112 or @dfn{insn notes} (to distinguish them from @dfn{reg notes}).
138 Before any edge is made @dfn{fall-thru}, the existence of such
148 @dfn{GIMPLE statement iterators} (GSIs). Grep for @code{^gsi}
194 When walking the edges in an edge vector, @dfn{edge iterators} should
258 starts a new basic block. In this case a @dfn{fall-thru} edge links
416 GCC can handle profile information obtained through @dfn{profile
483 destination basic block is called @dfn{reverse probability} and is not
[all …]
|
| H A D | cpp.texi | 180 The C preprocessor, often known as @dfn{cpp}, is a @dfn{macro processor}
183 you to define @dfn{macros}, which are brief abbreviations for longer
247 processing. That set is what the C standard calls the @dfn{source}
260 converted again, into the @dfn{execution} character set. This
361 @dfn{backslash-newline}.
374 There are two kinds of comments. @dfn{Block comments} begin with
382 @dfn{Line comments} begin with @samp{//} and continue to the end of the
457 converted into a sequence of @dfn{preprocessing tokens}. These mostly
491 @dfn{identifier} is the same as an identifier in C: any sequence of
516 A @dfn{preprocessing number} has a rather bizarre definition. The
[all …]
|
| H A D | ux.texi | 45 A good diagnostic is @dfn{actionable}: it should assist the user in
78 Warnings should have a good @dfn{signal-to-noise ratio}: we should have few
79 @dfn{false positives} (falsely issuing a warning when no warning is
80 warranted) and few @dfn{false negatives} (failing to issue a warning when
231 @dfn{caret} location, plus a start and a finish:
430 GCC's diagnostic subsystem can emit @dfn{fix-it hints}: small suggested
|
| H A D | tree-ssa.texi | 86 The operand scanner gathers two kinds of operands: @dfn{real} and
87 @dfn{virtual}. An operand for which @code{is_gimple_reg} returns true
109 variable @code{b}. Real definition are also known as @dfn{killing
118 @dfn{must definition} of that variable. However, if a statement is only
121 then we mark that statement as having a @dfn{may definition}. For
166 that variable. In this case we refer to it as a @dfn{may definition}
167 or @dfn{aliased store}. The presence of the second copy of the
487 @dfn{PHI function} or @dfn{PHI node}. This new definition merges
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/doc/ |
| H A D | configterms.texi | 17 are building on (@dfn{build}), the machine that you are building for
18 (@dfn{host}), and the machine that GCC will produce code for
19 (@dfn{target}). When you configure GCC, you specify these with
27 @dfn{native}. If build and host are the same but target is different,
28 this is called a @dfn{cross}. If build, host, and target are all
29 different this is called a @dfn{canadian} (for obscure reasons dealing
33 different system. Some people call this a @dfn{host-x-host},
34 @dfn{crossed native}, or @dfn{cross-built native}. If build and target
38 There is a proposal to call this a @dfn{crossback}.
|
| H A D | standards.texi | 69 This standard, in both its forms, is commonly known as @dfn{C89}, or
70 occasionally as @dfn{C90}, from the dates of ratification.
85 as @dfn{AMD1}; the amended standard is sometimes known as @dfn{C94} or
86 @dfn{C95}. To select this standard in GCC, use the option
91 9899:1999, and is commonly known as @dfn{C99}. (While in
93 @dfn{C9X}.) GCC has substantially
102 A fourth version of the C standard, known as @dfn{C11}, was published
104 standard version were referred to as @dfn{C1X}.)
109 known as @dfn{C17} and is supported with @option{-std=c17} or
114 A further version of the C standard, known as @dfn{C2X}, is under
[all …]
|
| H A D | frontends.texi | 22 The abbreviation @dfn{GCC} has multiple meanings in common use. The
27 of the @dfn{language-independent} component of GCC: code shared among the
59 sort of preprocessor should not be confused with the @dfn{C
|
| H A D | cfg.texi | 96 instruction (the @dfn{head}) and the last instruction (the @dfn{tail})
97 or @dfn{end} of the instruction stream contained in a basic block. In
111 contains not only the ``real'' instructions, but also @dfn{notes}
112 or @dfn{insn notes} (to distinguish them from @dfn{reg notes}).
138 Before any edge is made @dfn{fall-thru}, the existence of such
148 @dfn{GIMPLE statement iterators} (GSIs). Grep for @code{^gsi}
194 When walking the edges in an edge vector, @dfn{edge iterators} should
258 starts a new basic block. In this case a @dfn{fall-thru} edge links
416 GCC can handle profile information obtained through @dfn{profile
483 destination basic block is called @dfn{reverse probability} and is not
[all …]
|
| H A D | cpp.texi | 180 The C preprocessor, often known as @dfn{cpp}, is a @dfn{macro processor}
183 you to define @dfn{macros}, which are brief abbreviations for longer
247 processing. That set is what the C standard calls the @dfn{source}
260 converted again, into the @dfn{execution} character set. This
361 @dfn{backslash-newline}.
374 There are two kinds of comments. @dfn{Block comments} begin with
382 @dfn{Line comments} begin with @samp{//} and continue to the end of the
457 converted into a sequence of @dfn{preprocessing tokens}. These mostly
491 @dfn{identifier} is the same as an identifier in C: any sequence of
516 A @dfn{preprocessing number} has a rather bizarre definition. The
[all …]
|
| H A D | ux.texi | 45 A good diagnostic is @dfn{actionable}: it should assist the user in
78 Warnings should have a good @dfn{signal-to-noise ratio}: we should have few
79 @dfn{false positives} (falsely issuing a warning when no warning is
80 warranted) and few @dfn{false negatives} (failing to issue a warning when
256 @dfn{caret} location, plus a start and a finish:
455 GCC's diagnostic subsystem can emit @dfn{fix-it hints}: small suggested
|
| H A D | tree-ssa.texi | 86 The operand scanner gathers two kinds of operands: @dfn{real} and
87 @dfn{virtual}. An operand for which @code{is_gimple_reg} returns true
109 variable @code{b}. Real definition are also known as @dfn{killing
118 @dfn{must definition} of that variable. However, if a statement is only
121 then we mark that statement as having a @dfn{may definition}. For
166 that variable. In this case we refer to it as a @dfn{may definition}
167 or @dfn{aliased store}. The presence of the second copy of the
475 @dfn{PHI function} or @dfn{PHI node}. This new definition merges
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/doc/ |
| H A D | whatis.texi | 25 the network (users and services, usually called @dfn{principals}). All
68 In Kerberos, principals use @dfn{tickets} to prove that they are who
81 of the ticket (@var{life}), and a secret @dfn{session key}
132 It would be possible to add a @dfn{replay cache}
145 called @dfn{mutual authentication}.
148 messages sent between @var{A} and @var{B} (known as @dfn{message
149 integrity}). Encryption can also be added (@dfn{message
|
| /netbsd-src/external/bsd/am-utils/dist/doc/ |
| H A D | am-utils.texi | 350 An @dfn{automounter} maintains a cache of mounted filesystems.
356 @dfn{selectors}. Selectors allow decisions of the form ``hostname is
359 types, including NFS, UFS and the novel @dfn{program} filesystem. The
426 @dfn{demand-mounted} when they are first referenced, and unmounted after
438 @i{Amd} supports the notion of @dfn{replicated} filesystems by evaluating
483 @dfn{volumes}. Here the term @dfn{volume} is used to refer to a
491 volume, then a @dfn{sublink} is used to refer to the sub-directory
534 forms of binding between names and files are provided. A @dfn{hard
536 @dfn{soft link} delays the binding until the name is accessed. An
537 @dfn{automounter} adds a further form in which the binding of name to
[all …]
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/kadm5/ |
| H A D | ipropd_master.c | 677 char *dfn; in send_complete() local
679 ret = asprintf(&dfn, "%s/ipropd.dumpfile", hdb_db_dir(context)); in send_complete()
680 if (ret == -1 || !dfn) { in send_complete()
685 fd = open(dfn, O_CREAT|O_RDWR, 0600); in send_complete()
688 krb5_warn(context, ret, "Cannot open/create iprop dumpfile %s", dfn); in send_complete()
689 free(dfn); in send_complete()
692 free(dfn); in send_complete()
|
| /netbsd-src/external/gpl2/texinfo/dist/doc/ |
| H A D | info-stnd.texi | 91 @dfn{Info} is a program which is used to view Info files on an ASCII
92 terminal. @dfn{Info files} are the result of processing Texinfo files
373 can take a @dfn{numeric} argument (see @ref{Miscellaneous Commands,
649 lines which are longer than the screen width @dfn{wrap}, i.e., they are
674 @dfn{pointers} which describe where the next, previous, and up nodes
880 default of the current node. @dfn{Killing} a node means that Info tries
1017 @dfn{Incremental searching} is similar to basic searching, but the
1056 @dfn{cross references}, or @dfn{xrefs} for short.
1067 @dfn{label}; it is the name that you can use to refer to the cross
1068 reference, and the second is the @dfn{target}; it is the full name of
[all …]
|
| /netbsd-src/external/gpl2/groff/dist/doc/ |
| H A D | groff.texinfo | 583 work using a @dfn{batch} paradigm: The input (or @dfn{source}) files are
588 Likewise, @code{groff} should not be confused with a @dfn{word
821 @dfn{macro} facility to specify how certain routine operations
823 should be done. These macros can be collected together into a @dfn{macro
837 Therefore, programs called @dfn{preprocessors} were written which
1387 Macro files are kept in the @dfn{tmac directories}, all of which
1388 constitute the @dfn{tmac path}. The elements of the search path for
1457 All font files are kept in the @dfn{font directories} which constitute
1458 the @dfn{font path}. The file search functions will always append the
1675 (@dfn{requests} and @dfn{escapes}), which tell @code{gtroff} how to
[all …]
|
| /netbsd-src/external/gpl3/binutils.old/dist/gas/doc/ |
| H A D | c-xgate.texi | 105 @table @dfn
152 @table @dfn
|
| /netbsd-src/external/gpl3/binutils/dist/gas/doc/ |
| H A D | c-xgate.texi | 105 @table @dfn
152 @table @dfn
|
| /netbsd-src/external/gpl3/binutils/dist/libctf/doc/ |
| H A D | ctf-spec.texi | 57 CTF dictionaries can be @dfn{children} of other dictionaries, in a
77 There are two major pieces to CTF: the @dfn{archive} and the
78 @dfn{dictionary}. Some relatives and ancestors of CTF call dictionaries
79 @dfn{containers}: the archive format is unique to this variant of CTF.
91 The CTF dictionary consists of a @dfn{preamble}, which does not vary
92 between versions of the CTF file format, and a @dfn{header} and some
93 number of @dfn{sections}, which can vary between versions.
125 with a @dfn{default name}, @code{.ctf} (which can be represented as
545 describes a type of some @dfn{kind}: each kind of type has some amount of
612 @tab The @dfn{info word}, containing information on the kind of this type, its
[all …]
|