Hi, 2011/11/10 Måns Rullgård <[email protected]>: > Sean McGovern <[email protected]> writes: >> valgrind is not fond of the pointer math in hScale_altivec_real(), > > This is a weird description. Valgrind never complains about pointer > maths as such, only about actual memory accesses. I'm guessing it has > to do with loading from an unaligned array, which will overread the end > up to a 16-byte aligned position.
The array is aligned. Doesn't it just read 32 pixels at once, i.e. the FFALIGN(width, 16) should be changed to 32? Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
