| /openbsd-src/games/battlestar/ |
| H A D | dayfile.c | 9 * modification, are permitted provided that the following conditions
10 * are met:
23 * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
38 { "You are in the main hangar.",
40 "This is a huge bay where many fighters and cargo craft lie. Alarms are \n\
41 sounding and fighter pilots are running to their ships. Above is a gallery\n\
47 "Ships are landing here, some heavily damaged. Enemy fighters continually\n\
51 { "You are in the gallery.",
54 is near destruction. Fires are spreading out of control and laser blasts\n\
57 { "You are in the control room.",
[all …]
|
| H A D | nightfile.c | 9 * modification, are permitted provided that the following conditions
10 * are met:
23 * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
38 { "You are in the main hangar.",
40 "This is a huge bay where many fighters and cargo craft lie. Alarms are \n\
41 sounding and fighter pilots are running to their ships. Above is a gallery\n\
47 "Ships are landing here, some heavily damaged. Enemy fighters continually\n\
51 { "You are in the gallery.",
54 is near destruction. Fires are spreading out of control and laser blasts\n\
57 { "You are in the control room.",
[all …]
|
| /openbsd-src/gnu/gcc/gcc/doc/ |
| H A D | configterms.texi | 11 be confusing to anyone who doesn't know why things are the way they are.
12 While there are other documents which describe the configuration process
13 in detail, here are a few things that everyone working on GCC should
16 There are three system names that the build knows about: the machine you
17 are building on (@dfn{build}), the machine that you are building for
26 If build, host, and target are all the same, this is called a
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
31 on the build at that time). If host and target are the same, but build
32 is different, you are using a cross-compiler to build a native for a
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/doc/ |
| H A D | configterms.texi | 11 be confusing to anyone who doesn't know why things are the way they are.
12 While there are other documents which describe the configuration process
13 in detail, here are a few things that everyone working on GCC should
16 There are three system names that the build knows about: the machine you
17 are building on (@dfn{build}), the machine that you are building for
26 If build, host, and target are all the same, this is called a
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
31 on the build at that time). If host and target are the same, but build
32 is different, you are using a cross-compiler to build a native for a
[all …]
|
| /openbsd-src/usr.bin/bc/USD.doc/ |
| H A D | bc | 7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
25 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
62 These routines are themselves based on a dynamic storage allocator.
76 Some of the uses of this compiler are
93 collection of routines (called DC [5]) which are capable of doing
149 parentheses are interpreted just as in
152 Contents of parentheses are evaluated before material
154 Exponentiations are
163 are equivalent, as are the two expressions
[all …]
|
| /openbsd-src/share/man/man4/ |
| H A D | envy.4 | 31 The following sound cards are currently supported:
56 There are 8 streams corresponding to data received by the
58 They are labelled
63 There are 8 streams corresponding to data sent by the device to the codecs.
64 They are labelled
80 There are 2 streams that can be configured to contain any linear
82 They are labelled
86 From the mixer's point of view they are input streams,
90 There are 10 streams corresponding to samples transferred
92 They are labelled
[all …]
|
| H A D | termios.4 | 8 .\" modification, are permitted provided that the following conditions
9 .\" are met:
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
60 seldom open these files; they are opened by special programs, such
88 login shell are in the same session, and inherit the controlling
128 Orphaned process groups are immune to keyboard generated stop
167 terminal, read operations are allowed.
192 terminal, write operations are allowed.
221 Certain calls that set terminal parameters are treated in the same
249 Two general kinds of input processing are available, determined by
[all …]
|
| /openbsd-src/usr.bin/mklocale/ |
| H A D | mklocale.1 | 13 .\" modification, are permitted provided that the following conditions
14 .\" are met:
27 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
69 C-style comments are used
72 The following options are available:
81 the following are valid tokens in
122 The follow characters are taken literally:
127 All are equivalent.
130 All are equivalent.
136 Key words which should only appear once are:
[all …]
|
| /openbsd-src/gnu/usr.bin/perl/dist/Attribute-Handlers/t/ |
| H A D | data_convert.t | 17 sub test1 :Loud(till=>ears=>are=>bleeding) {
18 [qw(till ears are bleeding)]
21 sub test2 :Loud(['till','ears','are','bleeding']) {
22 [[qw(till ears are bleeding)]]
25 sub test3 :Loud(qw/till ears are bleeding/) {
26 [qw(till ears are bleeding)]
29 sub test4 :Loud(qw/my, ears, are, bleeding/) {
30 [('my,', 'ears,', 'are,', 'bleeding')]
33 sub test5 :Loud(till,ears,are,bleeding) {
34 [qw(till ears are bleeding)]
[all …]
|
| /openbsd-src/usr.bin/dc/USD.doc/ |
| H A D | dc | 7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
25 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
91 for the compiler interface and are not easy for a human user
94 Numbers that are typed into DC are put on a push-down
105 Here we describe the DC commands that are intended
106 for use by people. The additional commands that are
107 intended to be invoked by compiled output are
110 Any number of commands are permitted on a line.
111 Blanks and new-line characters are ignored except within numbers
[all …]
|
| /openbsd-src/lib/libcrypto/man/ |
| H A D | EVP_PKEY_meth_new.3 | |
| /openbsd-src/usr.sbin/nsd/ |
| H A D | nsd-control.8.in | 19 command and displays the result. Commands that require a reload are queued
22 The available options are:
35 There are several commands that the server understands.
55 and apply the changes to add and remove zones that are mentioned in the config.
56 Other changes are not applied, such as listening ip address and port and chroot,
57 also per-zone statistics are not applied.
59 zones (request\-xfr, zonefile, notify, ...) are updated. Also new
60 patterns are available for use with the addzone command.
112 changed (via AXFR or IXFR) are written, or if the zonefile has not been
114 path are created if necessary. With argument that zone is written if it
[all …]
|
| /openbsd-src/bin/cp/ |
| H A D | cp.1 | 11 .\" modification, are permitted provided that the following conditions
12 .\" are met:
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
68 file are copied to the destination
70 The names of the files themselves are not changed.
75 The options are as follows:
93 option is also specified, symbolic links on the command line are followed.
94 Symbolic links encountered in the tree traversal are not followed.
109 option is also specified, all symbolic links are followed.
113 option is also specified, no symbolic links are followed.
[all …]
|
| /openbsd-src/gnu/llvm/clang/docs/ |
| H A D | ConstantInterpreter.rst | 12 clang, improving performance on constructs which are executed inefficiently
24 one to directly evaluate expressions as they are compiled, without
25 generating bytecode (``EvalEmitter``). All functions are compiled to
26 bytecode, while toplevel expressions used in constant contexts are directly
34 description of opcodes, can be found in ``Opcodes.td``. The opcodes are
50 implement integral types which are required by the target, but are not
96 records (structs and classes). Unions are represented as records, except
98 fields are kept until they are reactivated and overwritten.
100 (``__attribute((vector_size(16)))``) are treated as arrays.
108 ``InterpFrame`` objects storing the call frames. Frames are built by
[all …]
|
| /openbsd-src/gnu/llvm/llvm/include/llvm/Transforms/Utils/ |
| H A D | FunctionComparator.h | 10 // are used by the MergeFunctions pass for comparing functions.
45 /// globals need to maintain their relative order. Globals are assigned a number
46 /// when they are first visited. This order is deterministic, and so the
47 /// assigned numbers are as well. When two functions are merged, neither number
48 /// is updated. If the symbols are weak, this would be incorrect. If they are
92 /// side of claiming that two functions are different).
130 /// Stage 0: If types are equal in terms of cmpTypes, then we can go straight
134 /// Stage 1: Types that satisfies isFirstClassType conditions are always
137 /// If both types are vectors, then vector with greater bitwidth is
139 /// If both types are vectors with the same bitwidth, then types
[all …]
|
| /openbsd-src/lib/libkeynote/ |
| H A D | keynote.4 | 40 Details on the API, assertion syntax, and command-line tool are given in
59 which are operations with security consequences that are
64 which are entities that can be authorized to perform actions.
68 which govern the actions that principals are authorized to perform.
90 Furthermore, policies and credentials are written in standard languages
91 that are shared by all trust-managed applications; the security configuration
94 themselves are quite different.
96 Trust-management policies are easy to distribute across networks, helping
112 KeyNote assertions are essentially small, highly-structured programs.
117 the same syntax as policy assertions but are also signed by the principal
[all …]
|
| /openbsd-src/usr.sbin/unbound/ |
| H A D | README-Travis.md | 5 …and above, and includes NDK-r20 and NDK-r21. Mips and Mips64 are not tested because they are no lo…
13 …le-endian platform, and s390x is a big-endian platform. There are pairs of recipes that are simila…
32 …are tested using Clang and GCC, for a total of four builds. The first sanitizer is Undefined Behav…
34 The recipes are similar to the following.
69 Travis tests Android builds for the armv7a, aarch64, x86 and x86_64 architectures. The builds are t…
96 …are working from a developer machine you probably already have the necessary tools installed. You …
116 If you are working from a developer machine you probably already have a NDK and SDK installed.
120 …are available to the calling shell. The script sets variables like `CC`, `CXX`, `AS` and `AR`; set…
142 …are built for Android using the scripts `contrib/android/install_openssl.sh` and `contrib/android/…
144 …ystem headers and libraries for an architecture. Typical `PKG_CONFIG_PATH` are `$HOME/android23-ar…
[all …]
|
| /openbsd-src/lib/libc/time/ |
| H A D | strptime.3 | 9 .\" modification, are permitted provided that the following conditions
10 .\" are met:
20 .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
68 The following conversion specifications are supported:
85 the century number [0,99]; leading zeros are permitted but not required.
91 leading zeros are permitted but not required.
96 leading spaces or zeros are permitted but not required.
111 leading zeros are permitted but not required.
114 leading zeros are permitted but not required.
117 leading zeros are permitted but not required.
[all …]
|
| /openbsd-src/gnu/usr.bin/perl/pod/ |
| H A D | perlsecpolicy.pod | 43 team handles. General guidelines about how this is determined are
44 detailed in the L</WHAT ARE SECURITY ISSUES> section.
54 go through are explained in the L</HOW WE DEAL WITH SECURITY ISSUES>
57 =head1 WHAT ARE SECURITY ISSUES
83 The Perl modules shipped with the interpreter that are developed in the core
88 The command line tools shipped with the interpreter that are developed in the
93 Files under the F<cpan/> directory in Perl's repository and release tarballs are
138 There are certain categories of bugs that are frequently reported to
141 The following is a list of commonly reported bugs that are not
166 L<Opcode> restrictions and L<Safe> compartments are not supported as
[all …]
|
| /openbsd-src/sbin/fsck/ |
| H A D | fsck.8 | 7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
17 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
53 If no file systems are specified,
58 Only partitions in fstab that are mounted
62 and that have non-zero pass numbers are checked.
63 File systems with pass number 1 (normally just the root file system) are
65 When pass 1 completes, all remaining file systems are checked, with one
70 By default, file systems which are already mounted read/write are not
73 The options are as follows:
[all …]
|
| /openbsd-src/lib/libz/ |
| H A D | algorithm.doc | 7 length). Distances are limited to 32K bytes, and lengths are limited
13 Literals or match lengths are compressed with one Huffman tree, and
14 match distances are compressed with another tree. The trees are stored
21 Duplicated strings are found using a hash table. All input strings of
22 length 3 are inserted in the hash table. A hash index is computed for
24 strings in the chain are compared with the current input string, and
27 The hash chains are searched starting with the most recent strings, to
29 The hash chains are singly linked. There are no deletions from the
30 hash chains, the algorithm simply discards matches that are too old.
32 To avoid a worst-case situation, very long hash chains are arbitrarily
[all …]
|
| /openbsd-src/sbin/fsck_ffs/SMM.doc/ |
| H A D | 4.t | 8 .\" modification, are permitted provided that the following conditions
9 .\" are met:
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
62 it will only fix corruptions that are expected
64 These actions are a proper subset of the actions that
76 When preen'ing most errors are fatal.
77 For those that are expected,
82 The error conditions are organized by the
104 All the initialization errors are fatal
112 legal options are \-b, \-c, \-y, \-n, and \-p.
[all …]
|
| /openbsd-src/usr.bin/vi/docs/USD.doc/vi.ref/ |
| H A D | vi.ref | 47 which are implementations of the historic Berkeley
66 The vi program is freely redistributable. You are welcome to copy,
111 Portions of this document are reprinted and reproduced from
164 If you are in an unfamiliar environment,
171 There are a few features in
173 that are not found in historic versions of
175 Some of the more interesting of those features are briefly described
191 There are a few features in
193 that are not found in historic versions of
195 Some of the more interesting of these are as follows:
[all …]
|
| /openbsd-src/gnu/llvm/clang/lib/Headers/ |
| H A D | ammintrin.h | 34 /// The value from which bits are extracted.
36 /// Bits [5:0] specify the length; the other bits are ignored. If bits [5:0]
37 /// are zero, the length is interpreted as 64.
40 /// bits are ignored. If the sum of the index and length is greater than 64,
41 /// the result is undefined. If the length and index are both zero, bits
42 /// [63:0] of parameter \a x are extracted. If the length is zero but the
59 /// The value from which bits are extracted.
62 /// length at [5:0]; all other bits are ignored. If bits [5:0] are zero, the
64 /// greater than 64, the result is undefined. If the length and index are
65 /// both zero, bits [63:0] of parameter \a __x are extracted. If the length
[all …]
|
| /openbsd-src/gnu/llvm/clang/docs/analyzer/developer-docs/ |
| H A D | IPA.rst | 4 There are several options that control which calls the analyzer will consider for
22 determined at runtime and we are not 100% sure that our type info is
28 has code that is only exercised when some of its methods are overridden.
35 analyzer's configuration table, so they are all specified as follows:
66 Currently, template functions are considered for inlining by default.
82 Currently, C++ standard library functions are considered for inlining by
85 The standard library functions and the STL in particular are used ubiquitously
99 Currently, these constructors and destructors are NOT considered for inlining
103 named 'iterator' or a member named 'begin'; these names are idiomatic in C++,
115 Many of these issues are avoided if containers always have unknown, symbolic
[all …]
|