--- libecb/ecb.pod 2015/02/18 20:48:59 1.64 +++ libecb/ecb.pod 2020/01/20 13:41:18 1.77 @@ -60,15 +60,21 @@ ecb.h makes sure that the following types are defined (in the expected way): - int8_t uint8_t int16_t uint16_t - int32_t uint32_t int64_t uint64_t - intptr_t uintptr_t + int8_t uint8_ + int16_t uint16_t + int32_t uint32_ + int64_t uint64_t + int_fast8_t uint_fast8_t + int_fast16_t uint_fast16_t + int_fast32_t uint_fast32_t + int_fast64_t uint_fast64_t + intptr_t uintptr_t The macro C is defined to the size of a pointer on this platform (currently C<4> or C<8>) and can be used in preprocessor expressions. -For C and C use C. +For C and C use C/C. =head2 LANGUAGE/ENVIRONMENT/COMPILER VERSIONS @@ -91,20 +97,20 @@ Note that later versions (ECB_C11) remove core features again (for example, variable length arrays). -=item ECB_C11 +=item ECB_C11, ECB_C17 -True if the implementation claims to be compliant to C11 (ISO/IEC -9899:2011) or any later version, while not claiming to be C++. +True if the implementation claims to be compliant to C11/C17 (ISO/IEC +9899:2011, :20187) or any later version, while not claiming to be C++. =item ECB_CPP True if the implementation defines the C<__cplusplus__> macro to a true value, which is typically true for C++ compilers. -=item ECB_CPP11 +=item ECB_CPP11, ECB_CPP14, ECB_CPP17 -True if the implementation claims to be compliant to ISO/IEC 14882:2011 -(C++11) or any later version. +True if the implementation claims to be compliant to C++11/C++14/C++17 +(ISO/IEC 14882:2011, :2014, :2017) or any later version. =item ECB_GCC_VERSION (major, minor) @@ -244,15 +250,15 @@ =item ecb_deprecated_message (message) -Same as C, but if possible, supply a diagnostic that is +Same as C, but if possible, the specified diagnostic is used instead of a generic depreciation message when the object is being used. =item ecb_inline -Expands either to C or to just C, if inline -isn't supported. It should be used to declare functions that should be -inlined, for code size or speed reasons. +Expands either to (a compiler-specific equivalent of) C or +to just C, if inline isn't supported. It should be used to declare +functions that should be inlined, for code size or speed reasons. Example: inline this function, it surely will reduce codesize. @@ -264,7 +270,7 @@ =item ecb_noinline -Prevent a function from being inlined - it might be optimised away, but +Prevents a function from being inlined - it might be optimised away, but not inlined into other functions. This is useful if you know your function is rarely called and large enough for inlining not to be helpful. @@ -404,6 +410,12 @@ =over 4 +=item ECB_OPTIMIZE_SIZE + +Is C<1> when the compiler optimizes for size, C<0> otherwise. This symbol +can also be defined before including F, in which case it will be +unchanged. + =item bool ecb_is_constant (expr) Returns true iff the expression can be deduced to be a compile-time @@ -491,8 +503,9 @@ =item ecb_assume (cond) -Try to tell the compiler that some condition is true, even if it's not -obvious. +Tries to tell the compiler that some condition is true, even if it's not +obvious. This is not a function, but a statement: it cannot be used in +another expression. This can be used to teach the compiler about invariants or other conditions that might improve code generation, but which are impossible to @@ -523,7 +536,7 @@ This function does nothing itself, except tell the compiler that it will never be executed. Apart from suppressing a warning in some cases, this -function can be used to implement C or similar functions. +function can be used to implement C or similar functionality. =item ecb_prefetch (addr, rw, locality) @@ -535,6 +548,9 @@ need to be accessible (it could be a null pointer for example), but C and C must be compile-time constants. +This is a statement, not a function: you cannot use it as part of an +expression. + An obvious way to use this is to prefetch some data far away, in a big array you loop over. This prefetches memory some 128 array elements later, in the hope that it will be ready when the CPU arrives at that location. @@ -581,12 +597,17 @@ =item int ecb_ctz64 (uint64_t x) +=item int ecb_ctz (T x) [C++] + Returns the index of the least significant bit set in C (or equivalently the number of bits set to 0 before the least significant bit set), starting from 0. If C is 0 the result is undefined. For smaller types than C you can safely use C. +The overloaded C++ C function supports C, C, +C and C types. + For example: ecb_ctz32 (3) = 0 @@ -596,14 +617,21 @@ =item bool ecb_is_pot64 (uint32_t x) -Return true iff C is a power of two or C. +=item bool ecb_is_pot (T x) [C++] + +Returns true iff C is a power of two or C. -For smaller types then C you can safely use C. +For smaller types than C you can safely use C. + +The overloaded C++ C function supports C, C, +C and C types. =item int ecb_ld32 (uint32_t x) =item int ecb_ld64 (uint64_t x) +=item int ecb_ld64 (T x) [C++] + Returns the index of the most significant bit set in C, or the number of digits the number requires in binary (so that C<< 2**ld <= x < 2**(ld+1) >>). If C is 0 the result is undefined. A common use case is @@ -617,14 +645,22 @@ For smaller types than C you can safely use C. +The overloaded C++ C function supports C, C, +C and C types. + =item int ecb_popcount32 (uint32_t x) =item int ecb_popcount64 (uint64_t x) +=item int ecb_popcount (T x) [C++] + Returns the number of bits set to 1 in C. For smaller types than C you can safely use C. +The overloaded C++ C function supports C, C, +C and C types. + For example: ecb_popcount32 (7) = 3 @@ -636,14 +672,24 @@ =item uint32_t ecb_bitrev32 (uint32_t x) +=item T ecb_bitrev (T x) [C++] + Reverses the bits in x, i.e. the MSB becomes the LSB, MSB-1 becomes LSB+1 and so on. +The overloaded C++ C function supports C, C and C types. + Example: ecb_bitrev8 (0xa7) = 0xea ecb_bitrev32 (0xffcc4411) = 0x882233ff +=item T ecb_bitrev (T x) [C++] + +Overloaded C++ bitrev function. + +C must be one of C, C or C. + =item uint32_t ecb_bswap16 (uint32_t x) =item uint32_t ecb_bswap32 (uint32_t x) @@ -654,6 +700,9 @@ C after reversing the order of bytes (0x11223344 becomes 0x44332211 in C). +The overloaded C++ C function supports C, C, +C and C types. + =item uint8_t ecb_rotl8 (uint8_t x, unsigned int count) =item uint16_t ecb_rotl16 (uint16_t x, unsigned int count) @@ -678,32 +727,210 @@ to "optimal" code (e.g. a single C or a combination of C on x86). +=item T ecb_rotl (T x, unsigned int count) [C++] + +=item T ecb_rotr (T x, unsigned int count) [C++] + +Overloaded C++ rotl/rotr functions. + +C must be one of C, C, C or C. + +=back + +=head2 HOST ENDIANNESS CONVERSION + +=over 4 + +=item uint_fast16_t ecb_be_u16_to_host (uint_fast16_t v) + +=item uint_fast32_t ecb_be_u32_to_host (uint_fast32_t v) + +=item uint_fast64_t ecb_be_u64_to_host (uint_fast64_t v) + +=item uint_fast16_t ecb_le_u16_to_host (uint_fast16_t v) + +=item uint_fast32_t ecb_le_u32_to_host (uint_fast32_t v) + +=item uint_fast64_t ecb_le_u64_to_host (uint_fast64_t v) + +Convert an unsigned 16, 32 or 64 bit value from big or little endian to host byte order. + +The naming convention is C(C|C)C<_u>C<16|32|64>C<_to_host>, +where be and le stand for big endian and little endian, respectively. + +=item uint_fast16_t ecb_host_to_be_u16 (uint_fast16_t v) + +=item uint_fast32_t ecb_host_to_be_u32 (uint_fast32_t v) + +=item uint_fast64_t ecb_host_to_be_u64 (uint_fast64_t v) + +=item uint_fast16_t ecb_host_to_le_u16 (uint_fast16_t v) + +=item uint_fast32_t ecb_host_to_le_u32 (uint_fast32_t v) + +=item uint_fast64_t ecb_host_to_le_u64 (uint_fast64_t v) + +Like above, but converts I host byte order to the specified +endianness. + +=back + +In C++ the following additional template functions are supported: + +=over 4 + +=item T ecb_be_to_host (T v) + +=item T ecb_le_to_host (T v) + +=item T ecb_host_to_be (T v) + +=item T ecb_host_to_le (T v) + +These functions work like their C counterparts, above, but use templates, +which make them useful in generic code. + +C must be one of C, C, C or C +(so unlike their C counterparts, there is a version for C, which +again can be useful in generic code). + +=head2 UNALIGNED LOAD/STORE + +These function load or store unaligned multi-byte values. + +=over 4 + +=item uint_fast16_t ecb_peek_u16_u (const void *ptr) + +=item uint_fast32_t ecb_peek_u32_u (const void *ptr) + +=item uint_fast64_t ecb_peek_u64_u (const void *ptr) + +These functions load an unaligned, unsigned 16, 32 or 64 bit value from +memory. + +=item uint_fast16_t ecb_peek_be_u16_u (const void *ptr) + +=item uint_fast32_t ecb_peek_be_u32_u (const void *ptr) + +=item uint_fast64_t ecb_peek_be_u64_u (const void *ptr) + +=item uint_fast16_t ecb_peek_le_u16_u (const void *ptr) + +=item uint_fast32_t ecb_peek_le_u32_u (const void *ptr) + +=item uint_fast64_t ecb_peek_le_u64_u (const void *ptr) + +Like above, but additionally convert from big endian (C) or little +endian (C) byte order to host byte order while doing so. + +=item ecb_poke_u16_u (void *ptr, uint16_t v) + +=item ecb_poke_u32_u (void *ptr, uint32_t v) + +=item ecb_poke_u64_u (void *ptr, uint64_t v) + +These functions store an unaligned, unsigned 16, 32 or 64 bit value to +memory. + +=item ecb_poke_be_u16_u (void *ptr, uint_fast16_t v) + +=item ecb_poke_be_u32_u (void *ptr, uint_fast32_t v) + +=item ecb_poke_be_u64_u (void *ptr, uint_fast64_t v) + +=item ecb_poke_le_u16_u (void *ptr, uint_fast16_t v) + +=item ecb_poke_le_u32_u (void *ptr, uint_fast32_t v) + +=item ecb_poke_le_u64_u (void *ptr, uint_fast64_t v) + +Like above, but additionally convert from host byte order to big endian +(C) or little endian (C) byte order while doing so. + +=back + +In C++ the following additional template functions are supported: + +=over 4 + +=item T ecb_peek (const void *ptr) + +=item T ecb_peek_be (const void *ptr) + +=item T ecb_peek_le (const void *ptr) + +=item T ecb_peek_u (const void *ptr) + +=item T ecb_peek_be_u (const void *ptr) + +=item T ecb_peek_le_u (const void *ptr) + +Similarly to their C counterparts, these functions load an unsigned 8, 16, +32 or 64 bit value from memory, with optional conversion from big/little +endian. + +Since the type cannot be deduced, it has top be specified explicitly, e.g. + + uint_fast16_t v = ecb_peek (ptr); + +C must be one of C, C, C or C. + +Unlike their C counterparts, these functions support 8 bit quantities +(C) and also have an aligned version (without the C<_u> prefix), +all of which hopefully makes them more useful in generic code. + +=item ecb_poke (void *ptr, T v) + +=item ecb_poke_be (void *ptr, T v) + +=item ecb_poke_le (void *ptr, T v) + +=item ecb_poke_u (void *ptr, T v) + +=item ecb_poke_be_u (void *ptr, T v) + +=item ecb_poke_le_u (void *ptr, T v) + +Again, similarly to their C counterparts, these functions store an +unsigned 8, 16, 32 or z64 bit value to memory, with optional conversion to +big/little endian. + +C must be one of C, C, C or C. + +Unlike their C counterparts, these functions support 8 bit quantities +(C) and also have an aligned version (without the C<_u> prefix), +all of which hopefully makes them more useful in generic code. + =back =head2 FLOATING POINT FIDDLING =over 4 -=item ECB_INFINITY +=item ECB_INFINITY [-UECB_NO_LIBM] Evaluates to positive infinity if supported by the platform, otherwise to a truly huge number. -=item ECB_NAN +=item ECB_NAN [-UECB_NO_LIBM] Evaluates to a quiet NAN if supported by the platform, otherwise to C. -=item float ecb_ldexpf (float x, int exp) +=item float ecb_ldexpf (float x, int exp) [-UECB_NO_LIBM] Same as C, but always available. +=item uint32_t ecb_float_to_binary16 (float x) [-UECB_NO_LIBM] + =item uint32_t ecb_float_to_binary32 (float x) [-UECB_NO_LIBM] =item uint64_t ecb_double_to_binary64 (double x) [-UECB_NO_LIBM] These functions each take an argument in the native C or C -type and return the IEEE 754 bit representation of it. +type and return the IEEE 754 bit representation of it (binary16/half, +binary32/single or binary64/double precision). The bit representation is just as IEEE 754 defines it, i.e. the sign bit will be the most significant bit, followed by exponent and mantissa. @@ -717,7 +944,7 @@ be able to optimise away this function completely. These functions can be helpful when serialising floats to the network - you -can serialise the return value like a normal uint32_t/uint64_t. +can serialise the return value like a normal uint16_t/uint32_t/uint64_t. Another use for these functions is to manipulate floating point values directly. @@ -734,11 +961,12 @@ =item float ecb_binary32_to_float (uint32_t x) [-UECB_NO_LIBM] -=item double ecb_binary32_to_double (uint64_t x) [-UECB_NO_LIBM] +=item double ecb_binary64_to_double (uint64_t x) [-UECB_NO_LIBM] The reverse operation of the previous function - takes the bit -representation of an IEEE binary16, binary32 or binary64 number and -converts it to the native C or C format. +representation of an IEEE binary16, binary32 or binary64 number (half, +single or double precision) and converts it to the native C or +C format. This function should work even when the native floating point format isn't IEEE compliant, of course at a speed and code size penalty, and of course @@ -749,6 +977,19 @@ On all modern platforms (where C is true), the compiler should be able to optimise away this function completely. +=item uint16_t ecb_binary32_to_binary16 (uint32_t x) + +=item uint32_t ecb_binary16_to_binary32 (uint16_t x) + +Convert a IEEE binary32/single precision to binary16/half format, and vice +versa, handling all details (round-to-nearest-even, subnormals, infinity +and NaNs) correctly. + +These are functions are available under C<-DECB_NO_LIBM>, since +they do not rely on the platform floating point format. The +C and C functions are +usually what you want. + =back =head2 ARITHMETIC @@ -838,4 +1079,23 @@ =back +=head1 UNDOCUMENTED FUNCTIONALITY + +F is full of undocumented functionality as well, some of which is +intended to be internal-use only, some of which we forgot to document, and +some of which we hide because we are not sure we will keep the interface +stable. + +While you are welcome to rummage around and use whatever you find useful +(we can't stop you), keep in mind that we will change undocumented +functionality in incompatible ways without thinking twice, while we are +considerably more conservative with documented things. + +=head1 AUTHORS + +C is designed and maintained by: + + Emanuele Giaquinta + Marc Alexander Lehmann +