| /netbsd-src/external/bsd/openldap/dist/doc/guide/admin/ |
| H A D | appendix-ldap-result-codes.sdf | 49 Indicates that the operation is not properly sequenced with
58 Indicates the server received data that is not well-formed.
61 that the server does not support the requested protocol
65 indicate that the server does not support (by design or
70 be used to indicate that the server cannot ignore the order
71 of the controls as specified, or that the combination of the
76 Indicates that the time limit specified by the client was
81 Indicates that the size limit specified by the client was
86 Indicates that the Compare operation has successfully
92 Indicates that the Compare operation has successfully
[all …]
|
| /netbsd-src/external/gpl3/gcc/dist/libstdc++-v3/src/c++11/ |
| H A D | cow-stdexcept.cc | 32 _txnal_cow_string_C1_for_exceptions(void* that, const char* s, void* exc);
34 _txnal_cow_string_c_str(const void* that);
36 _txnal_cow_string_D1(void* that);
38 _txnal_cow_string_D1_commit(void* that);
244 _txnal_cow_string_C1_for_exceptions(void* that, const char* s, in _txnal_cow_string_C1_for_exceptions() argument
248 bs_type *bs = (bs_type*) that; in _txnal_cow_string_C1_for_exceptions()
306 _txnal_cow_string_c_str(const void* that) in _txnal_cow_string_c_str() argument
309 const bs_type *bs = (const bs_type*) that; in _txnal_cow_string_c_str()
316 _txnal_sso_string_c_str(const void* that) in _txnal_sso_string_c_str() argument
320 &((const std::__sso_string*) that)->_M_s._M_p)); in _txnal_sso_string_c_str()
[all …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/config/aarch64/ |
| H A D | constraints.md | 12 ;; GCC is distributed in the hope that it will be useful, but
33 since they will be reached by a BL that may have to go through a linker
56 "A constant that can be used with an ADD operation."
61 "@internal A constant that matches two uses of add instructions."
67 A constraint that matches a VG-based constant that can be added by
73 A constraint that matches a VG-based constant that can be added by
79 A constraint that matches a VG-based constant that can be added by
84 "A constant that can be used with a SUB operation (once negated)."
93 "A constant that can be used with a 32-bit logical operation."
98 "A constant that can be used with a 64-bit logical operation."
[all …]
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/config/aarch64/ |
| H A D | constraints.md | 12 ;; GCC is distributed in the hope that it will be useful, but
33 since they will be reached by a BL that may have to go through a linker
56 "A constant that can be used with an ADD operation."
61 "@internal A constant that matches two uses of add instructions."
67 A constraint that matches a VG-based constant that can be added by
73 A constraint that matches a VG-based constant that can be added by
79 A constraint that matches a VG-based constant that can be added by
84 "A constant that can be used with a SUB operation (once negated)."
93 "A constant that can be used with a 32-bit logical operation."
98 "A constant that can be used with a 64-bit logical operation."
[all …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/libstdc++-v3/src/c++11/ |
| H A D | cow-stdexcept.cc | 32 _txnal_cow_string_C1_for_exceptions(void* that, const char* s, void* exc);
34 _txnal_cow_string_c_str(const void* that);
36 _txnal_cow_string_D1(void* that);
38 _txnal_cow_string_D1_commit(void* that);
264 _txnal_cow_string_C1_for_exceptions(void* that, const char* s, in _txnal_cow_string_C1_for_exceptions() argument
268 bs_type *bs = (bs_type*) that; in _txnal_cow_string_C1_for_exceptions()
326 _txnal_cow_string_c_str(const void* that) in _txnal_cow_string_c_str() argument
329 const bs_type *bs = (const bs_type*) that; in _txnal_cow_string_c_str()
336 _txnal_sso_string_c_str(const void* that) in _txnal_sso_string_c_str() argument
340 &((const std::__sso_string*) that)->_M_s._M_p)); in _txnal_sso_string_c_str()
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/SystemZ/ |
| H A D | SystemZFeatures.td | 43 "Assume that the distinct-operands facility is installed"
48 "Assume that the fast-serialization facility is installed"
53 "Assume that the floating-point extension facility is installed"
58 "Assume that the high-word facility is installed"
63 "Assume that interlocked-access facility 1 is installed"
69 "Assume that the load/store-on-condition facility is installed"
75 "Assume that the population-count facility is installed"
80 "Assume that the message-security-assist extension facility 3 is installed"
85 "Assume that the message-security-assist extension facility 4 is installed"
90 "Assume that the reset-reference-bits-multiple facility is installed"
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/clang/docs/ |
| H A D | RefactoringEngine.rst | 6 a couple of examples that show how various primitives in the refactoring API
8 library provides several other APIs that are used when developing a
11 Refactoring engine can be used to implement local refactorings that are
14 refactorings that don't lend themselves well to source selection and/or have to
26 Clang's refactoring engine defines a set refactoring actions that implement
31 A refactoring action is a class that defines a list of related refactoring
57 grouped refactoring action rules that represent one refactoring operation.
64 that define a set of different rules that produce similar results. For example,
67 refactoring that works on all switches that operate on a particular enum, as
69 constant. To achieve that, we can create two different rules that will use one
[all …]
|
| H A D | PCHInternals.rst | 40 common set of headers that is included in nearly every source file in the
41 project, we *precompile* that bundle of headers into a single precompiled
43 load the PCH file first (as a prefix header), which acts as a stand-in for that
53 * The cost of generating the PCH file initially is not so large that it
78 this initial load is independent of the size of the AST file, such that a
81 only when it is referenced from the user's code, at which point only that
89 simple "Hello, World!" program that includes the Apple ``Cocoa.h`` header
117 out of all the headers that are very commonly used throughout your project, and
118 then create a PCH for every single source file in the project that includes the
119 code that is specific to that file, so that recompiling the file itself is very
[all …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/doc/ |
| H A D | compat.texi | 15 The set of runtime conventions followed by all of the tools that deal
23 A compiler conforms to an ABI if it generates code that follows all of
24 the specifications enumerated by that ABI@.
25 A library conforms to an ABI if it is implemented according to that ABI@.
26 An application conforms to an ABI if it is built using tools that conform
27 to that ABI and does not contain source code that specifically changes
31 Calling conventions are a subset of an ABI that specify of how arguments
35 Different sets of tools are interoperable if they generate files that
51 The features that are not covered by an ABI generally affect how a
92 Some GCC compilation options cause the compiler to generate code that
[all …]
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/doc/ |
| H A D | compat.texi | 15 The set of runtime conventions followed by all of the tools that deal
23 A compiler conforms to an ABI if it generates code that follows all of
24 the specifications enumerated by that ABI@.
25 A library conforms to an ABI if it is implemented according to that ABI@.
26 An application conforms to an ABI if it is built using tools that conform
27 to that ABI and does not contain source code that specifically changes
31 Calling conventions are a subset of an ABI that specify of how arguments
35 Different sets of tools are interoperable if they generate files that
51 The features that are not covered by an ABI generally affect how a
92 Some GCC compilation options cause the compiler to generate code that
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl/dist/crypto/engine/ |
| H A D | README.md | 4 This "description" (if one chooses to call it that) needed some major updating
16 I'll mention a bit about that first. EVP_CIPHER (and most of this applies
18 identifier that, in the current API, "lingers". These cipher description +
20 or can be loaded "en masse" into EVP storage so that they can be catalogued and
39 The important point about this is that EVP_CIPHER definitions and structures are
41 rewrites of many applications, to assume that EVP_CIPHERs can be reference
44 such ciphers is via entirely distinct API calls that didn't exist before.
46 pointer, that has been passed to the caller, is no longer being used.
52 hooking in ENGINEs is that multiple ENGINEs may implement the same ciphers. The
53 solution is necessarily that ENGINE-provided ciphers simply are not registered,
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl.old/dist/crypto/engine/ |
| H A D | README | 4 This "description" (if one chooses to call it that) needed some major updating
16 I'll mention a bit about that first. EVP_CIPHER (and most of this applies
18 identifier that, in the current API, "lingers". These cipher description +
20 or can be loaded "en masse" into EVP storage so that they can be catalogued and
39 The important point about this is that EVP_CIPHER definitions and structures are
41 rewrites of many applications, to assume that EVP_CIPHERs can be reference
44 such ciphers is via entirely distinct API calls that didn't exist before.
46 pointer, that has been passed to the caller, is no longer being used.
52 hooking in ENGINEs is that multiple ENGINEs may implement the same ciphers. The
53 solution is necessarily that ENGINE-provided ciphers simply are not registered,
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl/dist/providers/ |
| H A D | build.info | 4 # libfips.a Contains all algorithm implementations that should
8 # liblegacy.a Contains all algorithm implementations that should
12 # libdefault.a Contains all algorithm implementations that should
15 # To be noted is that the FIPS provider shares source code with libcrypto,
16 # which means that select source files from crypto/ are compiled for
23 # It is crucial that code that checks the FIPS_MODULE macro ends up in
25 # It is crucial that code that checks the STATIC_LEGACY macro ends up in
27 # It is recommended that code that is written for libcommon.a doesn't end
30 # Code in providers/implementations/ should be written in such a way that
61 # Strong dependencies. This ensures that any time an implementation library
[all …]
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/ |
| H A D | reg-notes.def | 11 GCC is distributed in the hope that it will be useful, but WITHOUT ANY
20 /* This file defines all the codes that may appear on individual
48 /* Describes the insn as a whole; it says that the insn sets a
56 could be used to hold that pseudo-register throughout the function. */
59 /* Like REG_EQUIV except that the destination is only momentarily
65 This is used in branches so that decrement and branch instructions
74 /* Points to a CODE_LABEL. Used by JUMP_INSNs to say that the CODE_LABEL
79 /* Points to a CODE_LABEL. Used by any insn to say that the CODE_LABEL
94 that this is a taken branch. The integer represents a value of
99 /* Attached to a call insn; indicates that the call is malloc-like and
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
| H A D | MemorySSA.rst | 11 ``MemorySSA`` is an analysis that allows us to cheaply reason about the
18 that something definitely cannot happen (for example, reason that a hoist
41 structure that maps ``Instruction``\ s to ``MemoryAccess``\ es, which are
55 ``MemoryDef/MemoryPhi`` which is the version of memory that the new
56 version is based on. This implies that there is a *single*
57 ``Def`` chain that connects all the ``Def``\ s, either directly
67 This means that ``d`` potentially clobbers (see below) ``c`` *or*
68 ``b`` *or* both. This in turn implies that without the use of `The walker`_,
72 point we have two (or more) ``MemoryDef``\ s that could flow into a
79 Note also that in SSA, Phi nodes merge must-reach definitions (that is,
[all …]
|
| H A D | Projects.rst | 12 projects that use LLVM header files, libraries, and tools. In order to use
15 * Set ``make`` variables. There are several variables that a ``Makefile`` needs
31 There are two ways that you can set all of these variables:
36 ``Makefiles``, a configure script that can be used to configure the location
48 code so that it can benefit from the build system's features. Mainly, you want
56 library that you build, you will have one directory in **lib** that will
57 contain that library's source code.
65 This subdirectory should contain any header files that are global to your
66 project. By global, we mean that they are used by more than one library or
77 For each program that you build, you will have one directory in **tools**
[all …]
|
| /netbsd-src/external/gpl2/gettext/dist/gettext-tools/src/ |
| H A D | read-catalog.h | 124 extern void default_constructor (abstract_catalog_reader_ty *that);
125 extern void default_destructor (abstract_catalog_reader_ty *that);
126 extern void default_parse_brief (abstract_catalog_reader_ty *that);
127 extern void default_parse_debrief (abstract_catalog_reader_ty *that);
128 extern void default_directive_domain (abstract_catalog_reader_ty *that,
130 extern void default_directive_message (abstract_catalog_reader_ty *that,
141 extern void default_comment (abstract_catalog_reader_ty *that, const char *s);
142 extern void default_comment_dot (abstract_catalog_reader_ty *that,
144 extern void default_comment_filepos (abstract_catalog_reader_ty *that,
146 extern void default_comment_special (abstract_catalog_reader_ty *that,
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/ |
| H A D | reg-notes.def | 11 GCC is distributed in the hope that it will be useful, but WITHOUT ANY
20 /* This file defines all the codes that may appear on individual
48 /* Describes the insn as a whole; it says that the insn sets a
56 could be used to hold that pseudo-register throughout the function. */
59 /* Like REG_EQUIV except that the destination is only momentarily
65 This is used in branches so that decrement and branch instructions
74 /* REG_CC_SETTER and REG_CC_USER link a pair of insns that set and use
77 of a branch as long as only one copy of the insn exists. In that
84 /* Points to a CODE_LABEL. Used by JUMP_INSNs to say that the CODE_LABEL
89 /* Points to a CODE_LABEL. Used by any insn to say that the CODE_LABEL
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/man7/ |
| H A D | passphrase-encoding.pod | 21 and stick to that throughout the lifetime of affected objects.
22 This means that for an object that was encrypted using a pass phrase encoded in
23 ISO-8859-1, that object needs to be decrypted using a pass phrase encoded in
30 The standard stipulates that the pass phrase shall be encoded as an ASN.1
42 to U+FFFF, but becomes an expansion for any other character), or failing that,
47 Assumes that the pass phrase is encoded in ASCII or ISO-8859-1 and
51 Note that since there is no check of your locale, this may produce UCS-2 /
52 UTF-16 characters that do not correspond to the original pass phrase characters
59 OpenSSL versions older than 1.1.0 do variant 2 only, and that is the reason why
62 It should be noted that this approach isn't entirely fault free.
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man7/ |
| H A D | passphrase-encoding.pod | 21 and stick to that throughout the lifetime of affected objects.
22 This means that for an object that was encrypted using a pass phrase encoded in
23 ISO-8859-1, that object needs to be decrypted using a pass phrase encoded in
30 The standard stipulates that the pass phrase shall be encoded as an ASN.1
42 to U+FFFF, but becomes an expansion for any other character), or failing that,
47 Assumes that the pass phrase is encoded in ASCII or ISO-8859-1 and
51 Note that since there is no check of your locale, this may produce UCS-2 /
52 UTF-16 characters that do not correspond to the original pass phrase characters
59 OpenSSL versions older than 1.1.0 do variant 2 only, and that is the reason why
62 It should be noted that this approach isn't entirely fault free.
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/rfc/ |
| H A D | rfc2649.txt | 32 create a secure journal of changes that have been made to each
36 that enable this functionality. It also defines an LDAP v3 schema
37 that allows for subsequent browsing of the journal information.
69 document is that the origin of the information that is stored in LDAP
70 v3 accessible directories is the LDAP v3 client that creates the
72 guaranteed by allowing for the digital signing of the operations that
75 an underlying session layer that provides such services, such as TLS.
76 Note that the integrity of an individual connection does not, in and
77 of itself guarantee the integrity of the data that comes across the
78 connection. This is due to the fact that the LDAP server is only
[all …]
|
| /netbsd-src/games/warp/ |
| H A D | config.h.SH | 21 * that running config.h.SH again will wipe out any changes you've made.
34 * This symbol, if defined, indicates that the program is running under
49 * This symbol, if defined, indicates to the C program that it should
55 * This symbol, if defined, indicates that the ftime() routine exists.
60 * This symbol, if defined, indicates that the C program may use the
65 * This symbol, if defined, indicates that the C program may use the
70 * This symbol, if defined, indicates that the C program may use the
79 * This symbol, if defined, indicates that the getpwent() routine
85 * This symbol, when defined, indicates that termlib-style routines
102 * This symbol, if defined, indicates that sys/ioctl.h exists and should
[all …]
|
| /netbsd-src/external/bsd/nvi/dist/cl/ |
| H A D | README.signal | 13 *probably* start blocking around any imported function that we don't know
18 can they handle interrupted system calls, so the vi routines that
19 call DB block signals. This means that DB routines could be
24 switched vi into ex mode, and we continue that practice.
29 that the screen will not resize until vi runs out of keys, but
30 that doesn't seem like a problem.
42 The up side is that there's no asynchronous behavior to worry about,
43 and obviously no reentrancy problems. The down side is that it's easy
52 the place -- I hate to litter the source code with that. For example,
61 the exception that flow control and signals are turned on, and curses
[all …]
|
| /netbsd-src/external/gpl3/binutils/dist/gprofng/src/ |
| H A D | QLParser.tab.hh | 336 swap (self_type& that) YY_NOEXCEPT
339 YY_ASSERT (*yytypeid_ == *that.yytypeid_);
340 std::swap (as<T> (), that.as<T> ());
348 move (self_type& that)
351 emplace<T> (std::move (that.as<T> ()));
354 swap<T> (that);
356 that.destroy<T> ();
363 move (self_type&& that)
365 emplace<T> (std::move (that.as<T> ()));
366 that.destroy<T> ();
[all …]
|
| /netbsd-src/crypto/dist/ipsec-tools/src/racoon/doc/ |
| H A D | README.plainrsa | 3 Before you begin, you should understand that the RSA authentication
5 by the public, the other readable only to you. Any data that is
7 private key, so that the private key user can be assured that the
10 decrypted by the public key so that the public knows that this
15 that the setup needs a pair of reasonably long keys for each host that
19 RSA authentication. For the purpose of this document, we assume that
27 RSA keys for the host. There are only two parameters that you should
31 seconds to generate keys that are 2048 bits long, and only slightly
39 2) When the process completes, you should have a text file that
45 of the output file that begins with "# pubkey=0sAQPAmBdT/" or
[all …]
|