Go to the documentation of this file.
36 for (j = 0; j <
height; j++) {
41 src_r[
i] =
r +
g - 0x80;
42 src_b[
i] =
b +
g - 0x80;
61 for (j = 0; j <
height; j++) {
66 src_r[
i] = (
r +
g - 0x200) & 0x3FF;
67 src_b[
i] = (
b +
g - 0x200) & 0x3FF;
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
static void restore_rgb_planes_c(uint8_t *src_r, uint8_t *src_g, uint8_t *src_b, ptrdiff_t linesize_r, ptrdiff_t linesize_g, ptrdiff_t linesize_b, int width, int height)
void ff_utvideodsp_init_x86(UTVideoDSPContext *c)
#define i(width, name, range_min, range_max)
static void restore_rgb_planes10_c(uint16_t *src_r, uint16_t *src_g, uint16_t *src_b, ptrdiff_t linesize_r, ptrdiff_t linesize_g, ptrdiff_t linesize_b, int width, int height)
av_cold void ff_utvideodsp_init(UTVideoDSPContext *c)