Home
last modified time | relevance | path

Searched refs:implementation (Results 1 – 25 of 633) sorted by relevance

12345678910>>...26

/freebsd-11-stable/sys/dev/bhnd/
HDbhnd_bus_if.m485 * the appropriate NVRAM child device, or to a parent bus implementation.
513 /** An implementation of bus_read_1() compatible with bhnd_resource */
521 /** An implementation of bus_read_2() compatible with bhnd_resource */
529 /** An implementation of bus_read_4() compatible with bhnd_resource */
537 /** An implementation of bus_write_1() compatible with bhnd_resource */
546 /** An implementation of bus_write_2() compatible with bhnd_resource */
555 /** An implementation of bus_write_4() compatible with bhnd_resource */
564 /** An implementation of bus_read_stream_1() compatible with bhnd_resource */
572 /** An implementation of bus_read_stream_2() compatible with bhnd_resource */
580 /** An implementation of bus_read_stream_4() compatible with bhnd_resource */
[all …]
/freebsd-11-stable/contrib/gcc/doc/
HDimplement-c.texi7 @cindex implementation-defined behavior, C language
9 A conforming implementation of ISO C is required to document its
11 ``implementation defined''. The following lists all such areas,
13 9899:1999 standards. Some areas are only implementation-defined in
27 * Translation implementation::
28 * Environment implementation::
29 * Identifiers implementation::
30 * Characters implementation::
31 * Integers implementation::
32 * Floating point implementation::
[all …]
HDstandards.texi35 @cindex freestanding implementation
37 @cindex hosted implementation
105 implementation. A @dfn{conforming hosted implementation} supports the
107 freestanding implementation} is only required to provide certain
117 implementation-defined, and a @dfn{hosted environment}, which is not
122 in a hosted implementation.
126 implementation, or as the compiler for a conforming hosted
127 implementation. By default, it will act as the compiler for a hosted
128 implementation, defining @code{__STDC_HOSTED__} as @code{1} and
131 freestanding implementation for a freestanding environment, use the
HDcompat.texi47 @item implementation-defined features
48 Language standards include lists of implementation-defined features whose
49 behavior can vary from one implementation to another. Some of these
55 Conformance to the same ABI and the same behavior of implementation-defined
94 different program behavior for implementation-defined features that are
97 usual behavior of implementation-defined features for the platform.
113 bugs in the implementation of the ABI in different compilers.
/freebsd-11-stable/usr.bin/sed/
HDPOSIX41 backslash in front of it. This implementation follows the BSD
50 implementation permits whitespace but does not require it.
54 POSIX. This implementation permits whitespace but does not
61 is a cleanup, and is followed by this implementation.
78 one might reverse the behaviour.) This implementation follows
86 command. This implementation follows historic practice and
99 This implementation follows historic practice.
107 any particular purpose, this implementation follows the POSIX
124 However, the current practice adopted by this implementation,
133 does not specify this. This implementation follows historical
[all …]
/freebsd-11-stable/crypto/openssl/doc/crypto/
HDEC_GFp_simple_method.pod26 implementation method must be provided. The functions described here all return a const pointer to …
27 …THOD> structure that can be passed to EC_GROUP_NEW. It is important that the correct implementation
30 For F2^m curves there is only one implementation choice, i.e. EC_GF2_simple_method.
32 For Fp curves the lowest common denominator implementation is the EC_GFp_simple_method implementati…
35 offers an implementation optimised for use with NIST recommended curves (NIST curves are available …
HDRSA_set_method.pod37 Initially, the default RSA_METHOD is the OpenSSL internal implementation,
59 This method may or may not be supplied by an ENGINE implementation, but if
61 RSA key itself is valid and does not have its implementation changed by
82 /* name of the implementation */
150 RSA_set_method() returns a pointer to the old RSA_METHOD implementation
/freebsd-11-stable/crypto/openssl/
HDREADME.ENGINE40 implementation supports, and for an application to directly feed string
70 behaviour in using a specific ENGINE implementation should be sent to the
71 author of that implementation (if it is mentioned in the corresponding C
76 implementation) then you should mail complete details to the relevant
93 select the ENGINE implementation you want.
98 ENGINE "control commands" so that each ENGINE implementation can provide
101 also) to provide any such input directly to the ENGINE implementation.
105 your helpdesk) to the specific ENGINE implementation (and device), and
123 you with a self-contained implementation in the form of a shared-library.
137 The dynamic ENGINE has a special flag in its implementation such that
[all …]
/freebsd-11-stable/contrib/llvm-project/llvm/lib/Support/
HDAtomic.cpp39 # error No memory fence implementation for your platform! in MemoryFence()
57 # error No compare-and-swap implementation for your platform! in CompareAndSwap()
/freebsd-11-stable/lib/libc/locale/
HDDESIGN.xlocale12 This document describes the implementation of these APIs for FreeBSD.
17 The overall goal of this implementation is to be compatible with the Darwin
35 implementation gives to this structure and so may be used by existing (bad) code.
44 differs from the Darwin implementation, which includes a deprecated
76 The existing locale implementation included several ad-hoc caching layers.
81 The current xlocale implementation removes the caching entirely. This pattern
100 rule. In the classic implementation, this function returns a pointer to some
157 in either this implementation or the Darwin one. You must call `duplocale()`
/freebsd-11-stable/contrib/llvm-project/llvm/lib/Support/Windows/
HDWatchdog.inc9 // This file provides the generic Windows implementation of the Watchdog class.
15 // on Windows. Roughly, a Windows implementation would use CreateWaitableTimer
/freebsd-11-stable/sys/contrib/octeon-sdk/cvmx-malloc/
HDREADME-malloc4 implementation of glibc. Source code and more information
11 In this implementation, memory regions must be explicitly
/freebsd-11-stable/contrib/openresolv/
HDREADME1 openresolv is a resolvconf implementation which manages resolv.conf
5 This resolvconf implementation, along with its subscribers, work with a
/freebsd-11-stable/contrib/openbsm/
HDREADME5 OpenBSM is an open source implementation of Sun's BSM event auditing file
15 Coupled with a kernel audit implementation, OpenBSM can be used to maintain
18 reusable in a kernel audit implementation, and may be found in the FreeBSD
/freebsd-11-stable/contrib/llvm-project/compiler-rt/lib/xray/
HDxray_profiling_flags.inc27 "Set to true if we want the profiling implementation to not write "
31 "implementation.")
/freebsd-11-stable/contrib/smbfs/
HDREADME3 SMB/CIFS protocol and SMB/CIFS file system implementation
7 It is a complete, kernel side implementation of SMB requester and filesystem.
/freebsd-11-stable/contrib/jemalloc/include/jemalloc/internal/
HDutil.h182 #error No implementation for size_t ffs() in ffs_zu()
195 #error No implementation for 64-bit ffs() in ffs_u64()
206 #error No implementation for 32-bit ffs() in ffs_u32()
/freebsd-11-stable/contrib/groff/
HDREADME.MinGW10 This file provides recommendations for building a Win32 implementation of
15 You require both the MinGW implementation of GCC and its supporting MSYS
16 toolkit, which provides a Win-32 implementation of the GNU bash shell, and a
107 o All of the MSYS tools, and the MinGW implementation of GCC, refer to files
166 In order to produce HTML output, you first require a working implementation
168 implementation for MS-Windows should be suitable, depending on your
225 implementation of the MS-Windows file system, and the manner in which the
226 Microsoft runtime library (which is used by the MinGW implementation of GCC)
235 GNU/Linux implementation of groff provides the GROFF_TMPDIR or TMPDIR
266 implementation of RXVT; it may be worked around by either starting MSYS
/freebsd-11-stable/contrib/sendmail/src/
HDhelpfile23 smtp To report bugs in the implementation see
83 send implementation.
86 soml otherwise mail. Not supported in this implementation.
90 saml implementation.
97 etrn <queuename> (implementation-specific).
/freebsd-11-stable/contrib/gdb/gdb/doc/
HDobserver.texi6 @cindex observers implementation rationale
19 The current implementation of the generic observer provides support
34 The observer implementation is also currently not reentrant.
/freebsd-11-stable/crypto/openssl/crypto/des/
HDCOPYRIGHT4 This package is an DES implementation written by Eric Young (eay@cryptsoft.com).
5 The implementation was written so as to conform with MIT's libdes.
50 implementation was a non-trivial and unpaid effort.
/freebsd-11-stable/crypto/openssl/crypto/engine/
HDREADME19 implementation structures can be defined or obtained directly by applications,
79 temporarily get and use the ENGINE's RSA implementation. Apart from being more
84 implementation and have its ENGINE pointer set to NULL.
90 of "cipher description" and less meaning in terms of "implementation". When an
99 context and so is used as the implementation. Pretty much how things work now
110 completely different implementation. Because this EVP_CIPHER isn't stored in the
126 implementation that the application loaded. It will *not* however link any
143 ENGINEs support. If each of those ENGINEs has a "des_cbc" implementation, we
161 not an interoperable implementation of "aes_256_cbc"), RSA_METHODs are
186 registered an implementation, the code will simply return NULL and the tb_rsa.c
/freebsd-11-stable/contrib/llvm-project/libcxx/include/
HDtypeinfo124 // This implementation of type_info assumes a unique copy of the RTTI for a
133 // This implementation of type_info does not assume there is always a unique
142 // This implementation of type_info does not assume always a unique copy of
153 // This implementation is specific to ARM64 on Apple platforms.
241 // this implementation is actually used.
/freebsd-11-stable/contrib/wpa/wpa_supplicant/
HDdefconfig115 # Note: The current EAP-TEAP implementation is experimental and should not be
117 # of conflicting statements and missing details and the implementation has
119 # any other implementation. This should not be used for anything else than
272 # Select program entry point implementation:
284 # Select event loop implementation
298 # Select layer 2 packet implementation
320 # Select TLS implementation
323 # internal = Internal TLSv1 implementation (experimental)
324 # linux = Linux kernel AF_ALG and internal TLSv1 implementation (experimental)
331 # implementation may not be compatible with TLS v1.1 message (ClientHello is
[all …]
/freebsd-11-stable/contrib/wpa/hostapd/
HDdefconfig114 # Note: The current EAP-TEAP implementation is experimental and should not be
116 # of conflicting statements and missing details and the implementation has
118 # any other implementation. This should not be used for anything else than
161 # Note: This is experimental and not complete implementation.
276 # Select TLS implementation
279 # internal = Internal TLSv1 implementation (experimental)
280 # linux = Linux kernel AF_ALG and internal TLSv1 implementation (experimental)
383 # Experimental implementation of draft-harkins-owe-07.txt

12345678910>>...26