Go to the documentation of this file.
29 const uint8_t *t1 =
src;
30 int half_size =
size / 2;
31 const uint8_t *t2 =
src + half_size;
35 for (
i = 0;
i < half_size;
i++) {
44 if ((
size & 1) == 0) {
50 for (ptrdiff_t
i = 1;
i <
size;
i += 2) {
static void reorder_pixels_scalar(uint8_t *dst, const uint8_t *src, ptrdiff_t size)
av_cold void ff_exrdsp_init(ExrDSPContext *c)
Undefined Behavior In the C some operations are like signed integer dereferencing freed accessing outside allocated Undefined Behavior must not occur in a C it is not safe even if the output of undefined operations is unused The unsafety may seem nit picking but Optimizing compilers have in fact optimized code on the assumption that no undefined Behavior occurs Optimizing code based on wrong assumptions can and has in some cases lead to effects beyond the output of computations The signed integer overflow problem in speed critical code Code which is highly optimized and works with signed integers sometimes has the problem that often the output of the computation does not c
uint8_t ptrdiff_t const uint8_t ptrdiff_t int intptr_t intptr_t int int16_t * dst
void ff_exrdsp_init_x86(ExrDSPContext *c)
The reader does not expect b to be semantically here and if the code is changed by maybe adding a a division or other the signedness will almost certainly be mistaken To avoid this confusion a new type was SUINT is the C unsigned type but it holds a signed int to use the same example SUINT a
static void predictor_scalar(uint8_t *src, ptrdiff_t size)
#define i(width, name, range_min, range_max)
void ff_exrdsp_init_riscv(ExrDSPContext *c)