From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCHv2 1/1] checkasm/lpc: test compute_autocorr
Date: Sun, 17 Dec 2023 23:57:50 +0200 (EET)
Message-ID: <4a48315-3857-81c6-11a-99a99db8ee4@martin.st> (raw)
In-Reply-To: <1728283.6a2RTAW4fK@basile.remlab.net>
On Sun, 17 Dec 2023, Rémi Denis-Courmont wrote:
> Le sunnuntaina 17. joulukuuta 2023, 18.09.45 EET James Almer a écrit :
>> On 12/17/2023 6:13 AM, Rémi Denis-Courmont wrote:
>> > ---
>> >
>> > tests/checkasm/lpc.c | 47 ++++++++++++++++++++++++++++++++++++++++++--
>> > 1 file changed, 45 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/tests/checkasm/lpc.c b/tests/checkasm/lpc.c
>> > index 592e34c03d..9b33f8a3b0 100644
>> > --- a/tests/checkasm/lpc.c
>> > +++ b/tests/checkasm/lpc.c
>> > @@ -57,10 +57,46 @@ static void test_window(int len)
>> >
>> > bench_new(src, len, dst1);
>> >
>> > }
>> >
>> > +static void test_compute_autocorr(ptrdiff_t len, int lag)
>> > +{
>> > + LOCAL_ALIGNED(32, double, src, [5000 + 2 + MAX_LPC_ORDER]);
>> > + LOCAL_ALIGNED(16, double, dst0, [MAX_LPC_ORDER + 1]);
>> > + LOCAL_ALIGNED(16, double, dst1, [MAX_LPC_ORDER + 1]);
>> > +
>> > + declare_func(void, const double *in, ptrdiff_t len, int lag, double
>> > *out); +
>> > + av_assert0(lag >= 0 && lag <= MAX_LPC_ORDER);
>> > +
>> > + for (int i = 0; i < MAX_LPC_ORDER; i++)
>> > + src[i] = 0.;
>> > +
>> > + src += MAX_LPC_ORDER;
>> > +
>> > + for (ptrdiff_t i = 0; i < len; i++) {
>> > + src[i] = (double)rnd() / (double)UINT_MAX;
>> > + }
>> > +
>> > + call_ref(src, len, lag, dst0);
>> > + call_new(src, len, lag, dst1);
>> > +
>> > + for (size_t i = 0; i < lag; i++) {
>> > + if (!double_near_abs_eps(dst0[i], dst1[i], EPS)) {
>>
>> checkasm: using random seed 2504816888
>> SSE2:
>> - lpc.apply_welch_window_even [OK]
>> - lpc.apply_welch_window_odd [OK]
>> 0: 770.224646270451 - 770.382378714191 = -0.15773244374
>> autocorr_10_sse2 (lpc.c:86)
>> - lpc.compute_autocorr_10 [FAILED]
>> 0: 807.574416481743 - 807.732148925482 = -0.157732443739
>> autocorr_30_sse2 (lpc.c:86)
>> - lpc.compute_autocorr_30 [FAILED]
>> 0: 787.329053288888 - 787.486785732628 = -0.15773244374
>> autocorr_32_sse2 (lpc.c:86)
>> - lpc.compute_autocorr_32 [FAILED]
>>
>> checkasm: using random seed 827008587
>> SSE2:
>> - lpc.apply_welch_window_even [OK]
>> - lpc.apply_welch_window_odd [OK]
>> - lpc.compute_autocorr_10 [OK]
>> - lpc.compute_autocorr_30 [OK]
>> - lpc.compute_autocorr_32 [OK]
>>
>> Some seeds work, others don't. So i guess EPS is too small
>
> Rounding errors would not cause a constant gap across the different test cases.
> This is most likely an off-by-one in the x86 code. I don't know if this is a
> bug in the x86 code, or the test case being a little loose with input
> parameters, and I have neither time, nor motivation not to mention skills to
> figure that out, so there will be no test cases for this function form me
> afterall.
FWIW, we've had these situations elsewhere before as well, in swscale,
where the existing x86 assembly mismatches the C code in nontrivial ways,
and we have new assembly (aarch64 in that case) that is missing a test
(even if one was written) due to this.
First I considered if we should collect these extra checkasm tests in some
branch somewhere, so they aren't lost, as they are useful when working on
assembly on other architectures.
But rather than having the code rot, forgotten in a stray branch
somewhere, I wonder if we should just go ahead and merge it with an #if
!ARCH_X86 or something, together with a notable FIXME comment.
That would keep the test coverage for new asm implementations, avoid code
rot, and leave the opportunity to sort things out easily available for
whoever wants to dissect the old existing x86 assembly implementations.
That's clearly not ideal, but would pragmatically be better than to just
not merge the new checkasm test at all. What do others think?
// Martin
_______________________________________________
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".
next prev parent reply other threads:[~2023-12-17 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 9:13 Rémi Denis-Courmont
2023-12-17 16:09 ` James Almer
2023-12-17 16:35 ` Rémi Denis-Courmont
2023-12-17 21:57 ` Martin Storsjö [this message]
2023-12-18 16:34 ` Rémi Denis-Courmont
2023-12-18 17:25 ` James Almer
2023-12-18 16:58 ` Anton Khirnov
2023-12-18 17:21 ` Michael Niedermayer
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=4a48315-3857-81c6-11a-99a99db8ee4@martin.st \
--to=martin@martin.st \
--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