--- cvsroot/libecb/ecb.pod 2015/02/18 20:29:27 1.62 +++ cvsroot/libecb/ecb.pod 2015/11/21 16:53:50 1.71 @@ -189,6 +189,22 @@ #define SQL_LIMIT 100 sql_exec ("select * from table limit " ECB_STRINGIFY (SQL_LIMIT)); +=item ECB_STRINGIFY_EXPR (expr) + +Like C, but additionally evaluates C to make sure it +is a valid expression. This is useful to catch typos or cases where the +macro isn't available: + + #include + + ECB_STRINGIFY (EDOM); // "33" (on my system at least) + ECB_STRINGIFY_EXPR (EDOM); // "33" + + // now imagine we had a typo: + + ECB_STRINGIFY (EDAM); // "EDAM" + ECB_STRINGIFY_EXPR (EDAM); // error: EDAM undefined + =back =head2 ATTRIBUTES @@ -228,7 +244,7 @@ =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. @@ -248,7 +264,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. @@ -475,8 +491,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 @@ -507,7 +524,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) @@ -519,6 +536,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. @@ -580,9 +600,9 @@ =item bool ecb_is_pot64 (uint32_t x) -Return true iff C is a power of two or 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. =item int ecb_ld32 (uint32_t x) @@ -668,26 +688,29 @@ =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_NON +=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. @@ -701,7 +724,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. @@ -718,11 +741,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 @@ -733,6 +757,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-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 @@ -822,4 +859,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 +