* [FFmpeg-devel] [PATCH] motion_est: fixed signed_integer_overflow when computing score
@ 2022-11-09 22:31 Thierry Foucu
2022-11-11 18:15 ` James Almer
0 siblings, 1 reply; 2+ messages in thread
From: Thierry Foucu @ 2022-11-09 22:31 UTC (permalink / raw)
To: ffmpeg-devel; +Cc: Thierry Foucu
---
libavcodec/motion_est.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/motion_est.c b/libavcodec/motion_est.c
index d17ffe42b4..95978d95dd 100644
--- a/libavcodec/motion_est.c
+++ b/libavcodec/motion_est.c
@@ -1571,7 +1571,7 @@ void ff_estimate_b_frame_motion(MpegEncContext * s,
type= CANDIDATE_MB_TYPE_BACKWARD_I;
}
- score= ((unsigned)(score*score + 128*256))>>16;
+ score= ((uint64_t)(score)*(uint64_t)(score) + 128*256)>>16;
c->mc_mb_var_sum_temp += score;
s->mc_mb_var[mb_y*s->mb_stride + mb_x] = score; //FIXME use SSE
}
--
2.38.1.493.g58b659f92b-goog
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [FFmpeg-devel] [PATCH] motion_est: fixed signed_integer_overflow when computing score
2022-11-09 22:31 [FFmpeg-devel] [PATCH] motion_est: fixed signed_integer_overflow when computing score Thierry Foucu
@ 2022-11-11 18:15 ` James Almer
0 siblings, 0 replies; 2+ messages in thread
From: James Almer @ 2022-11-11 18:15 UTC (permalink / raw)
To: ffmpeg-devel
On 11/9/2022 7:31 PM, Thierry Foucu wrote:
> ---
> libavcodec/motion_est.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/motion_est.c b/libavcodec/motion_est.c
> index d17ffe42b4..95978d95dd 100644
> --- a/libavcodec/motion_est.c
> +++ b/libavcodec/motion_est.c
> @@ -1571,7 +1571,7 @@ void ff_estimate_b_frame_motion(MpegEncContext * s,
> type= CANDIDATE_MB_TYPE_BACKWARD_I;
> }
>
> - score= ((unsigned)(score*score + 128*256))>>16;
> + score= ((uint64_t)(score)*(uint64_t)(score) + 128*256)>>16;
Is it not enough just doing
score= ((unsigned)score*score + 128*256)>>16;
If not, then use uint64_t, but like the above, you should only need to
cast score once.
> c->mc_mb_var_sum_temp += score;
> s->mc_mb_var[mb_y*s->mb_stride + mb_x] = score; //FIXME use SSE
> }
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-11-11 18:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-09 22:31 [FFmpeg-devel] [PATCH] motion_est: fixed signed_integer_overflow when computing score Thierry Foucu
2022-11-11 18:15 ` James Almer
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git