From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] checkasm: h264dsp: Avoid out of buffer writes when benchmarking
Date: Tue, 21 May 2024 14:42:18 +0300
Message-ID: <AF276138-D991-4336-A8E3-AB375D46807A@remlab.net> (raw)
In-Reply-To: <20240521110453.88641-1-martin@martin.st>
Le 21 mai 2024 14:04:53 GMT+03:00, "Martin Storsjö" <martin@martin.st> a écrit :
>The loop filters can write before the pointer given to them;
>the actual test invocations correctly used an offset, while
>the benchmark calls were lacking an offset. Therefore, when
>running with benchmarking, these tests could have spurious
>failures.
>---
> tests/checkasm/h264dsp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/tests/checkasm/h264dsp.c b/tests/checkasm/h264dsp.c
>index 0cc1f32740..67b8dce53c 100644
>--- a/tests/checkasm/h264dsp.c
>+++ b/tests/checkasm/h264dsp.c
>@@ -362,7 +362,7 @@ static void check_loop_filter(void)
> tc0[j][0], tc0[j][1], tc0[j][2], tc0[j][3]); \
> fail(); \
> } \
>- bench_new(dst1, 32, alphas[j], betas[j], tc0[j]); \
>+ bench_new(dst1 + off, 32, alphas[j], betas[j], tc0[j]);\
> } \
> } \
> } while (0)
>@@ -421,7 +421,7 @@ static void check_loop_filter_intra(void)
> j, alphas[j], betas[j]); \
> fail(); \
> } \
>- bench_new(dst1, 32, alphas[j], betas[j]); \
>+ bench_new(dst1 + off, 32, alphas[j], betas[j]); \
> } \
> } \
> } while (0)
LGTM
_______________________________________________
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".
prev parent reply other threads:[~2024-05-21 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 11:04 Martin Storsjö
2024-05-21 11:42 ` Rémi Denis-Courmont [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AF276138-D991-4336-A8E3-AB375D46807A@remlab.net \
--to=remi@remlab.net \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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