On Thu, Mar 2, 2023 at 6:37 AM James Almer wrote:
>
> On 3/2/2023 8:33 AM, James Almer wrote:
> > On 3/2/2023 6:05 AM, Anton Khirnov wrote:
> >> Quoting Jeremy Dorfman (2023-03-01 19:50:08)
> >>> null pointer arithmetic is undefined behavior in C.
> >
On Wed, Mar 1, 2023 at 3:22 PM Jeremy Dorfman wrote:
>
> On Wed, Mar 1, 2023 at 2:07 PM James Almer wrote:
> >
> > On 3/1/2023 3:50 PM, Jeremy Dorfman wrote:
> > > null pointer arithmetic is undefined behavior in C.
> > > ---
> > > libavcodec
On Wed, Mar 1, 2023 at 2:07 PM James Almer wrote:
>
> On 3/1/2023 3:50 PM, Jeremy Dorfman wrote:
> > null pointer arithmetic is undefined behavior in C.
> > ---
> > libavcodec/h264dec.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
>
null pointer arithmetic is undefined behavior in C.
---
libavcodec/h264dec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/h264dec.c b/libavcodec/h264dec.c
index 2d691731c5..ef698f2630 100644
--- a/libavcodec/h264dec.c
+++ b/libavcodec/h264dec.c
@@ -912,8 +912,
Large rgb2yuv tables and high pixel values cause the intermediate
int32_t of ru*r + gu*g + bu*b to exceed INT_MAX, which is undefined
behavior. This causes libswscale built with LLVM -fsanitize=undefined to
assert. Using unsigned integers instead has defined behavior and
produces identical results,
ck as uninitialized, so I
don't think this is a false positive -- it doesn't appear to ever be
intentionally written.
Thanks,
-Jeremy
On Mon, Apr 8, 2019 at 9:33 AM James Almer wrote:
> On 4/8/2019 9:14 AM, Jeremy Dorfman via ffmpeg-devel wrote:
> > Otherwise, AV1 encodes wi
Otherwise, AV1 encodes with FFmpeg trigger use-of-uninitialized-value
warnings under MemorySanitizer, and the output buffer potentially
changes from run to run.
---
libavformat/av1.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/av1.c b/libavformat/av1.c
index a0aad436a6..5fde8df
