From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 1/6] lavc/arm: dont assign hevc_qpel functions for non-multiple of 8 widths
Date: Wed, 5 Jan 2022 10:30:38 +0200 (EET)
Message-ID: <69469eb7-e7ce-c839-c5e5-dcd58e45d7a7@martin.st> (raw)
In-Reply-To: <AM7PR03MB6660EE596B5FCE39ACB89CCE8F4B9@AM7PR03MB6660.eurprd03.prod.outlook.com>
On Wed, 5 Jan 2022, Andreas Rheinhardt wrote:
> J. Dekker:
>> The assembly is written assuming that the width is a multiple of 8.
>>
>> However the real issue is the functions were errorneously assigned to
>> the 2, 4, 6 & 12 widths. This behaviour never broke the decoder as
>> samples which trigger the functions for these widths have not been found
>> in the wild. This relies on the mappings in ff_hevc_pel_weight[].
>>
>> Signed-off-by: J. Dekker <jdek@itanimul.li>
>> ---
>> libavcodec/arm/hevcdsp_init_neon.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> This set has already been reviewed by Martin, sending to list for
>> transparency.
>>
>> diff --git a/libavcodec/arm/hevcdsp_init_neon.c b/libavcodec/arm/hevcdsp_init_neon.c
>> index 201a088dac..112edb5edd 100644
>> --- a/libavcodec/arm/hevcdsp_init_neon.c
>> +++ b/libavcodec/arm/hevcdsp_init_neon.c
>> @@ -270,7 +270,8 @@ av_cold void ff_hevc_dsp_init_neon(HEVCDSPContext *c, const int bit_depth)
>> put_hevc_qpel_uw_neon[3][1] = ff_hevc_put_qpel_uw_h1v3_neon_8;
>> put_hevc_qpel_uw_neon[3][2] = ff_hevc_put_qpel_uw_h2v3_neon_8;
>> put_hevc_qpel_uw_neon[3][3] = ff_hevc_put_qpel_uw_h3v3_neon_8;
>> - for (x = 0; x < 10; x++) {
>> + for (x = 3; x < 10; x++) {
>> + if (x == 4) continue;
>> c->put_hevc_qpel[x][1][0] = ff_hevc_put_qpel_neon_wrapper;
>> c->put_hevc_qpel[x][0][1] = ff_hevc_put_qpel_neon_wrapper;
>> c->put_hevc_qpel[x][1][1] = ff_hevc_put_qpel_neon_wrapper;
>>
>
> This patchset led to regressions; see e.g.
> http://fate.ffmpeg.org/report.cgi?time=20220104162724&slot=aarch64-linux-qemu-ubuntu-gcc-4.8
Indeed. I had only ran fate-checkasm while reviewing it, assuming that it
had been fully tested with fate-hevc by the patch author.
Instead of reverting the full 6 patch set, it's enough to revert a couple
patches out of it though (there's some cosmetic cleanup that we can keep
in for now). But I'm afraid we should disable the preexisting
ff_hevc_sao_band_filter_8x8_8_neon function too. It's currently only run
for the [0] case, which I think corresponds to width <= 8. But if that
case also must handle widths that aren't an even multiple of 8, we'd have
a lingering bug that isn't exercised by fate-hevc.
// 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".
prev parent reply other threads:[~2022-01-05 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 5:20 J. Dekker
2022-01-04 5:20 ` [FFmpeg-devel] [PATCH v3 2/6] Revert "arm: hevc_qpel: Fix the assembly to work with non-multiple of 8 widths" J. Dekker
2022-01-04 5:20 ` [FFmpeg-devel] [PATCH v3 3/6] lavc/aarch64: add hevc sao edge 16x16 J. Dekker
2022-01-04 5:20 ` [FFmpeg-devel] [PATCH v3 4/6] lavc/aarch64: add hevc sao edge 8x8 J. Dekker
2022-01-04 5:20 ` [FFmpeg-devel] [PATCH v3 5/6] lavc/aarch64: clean-up sao band 8x8 function formatting J. Dekker
2022-01-04 5:20 ` [FFmpeg-devel] [PATCH v3 6/6] lavc/aarch64: add hevc sao band 8x8 tiling J. Dekker
2022-01-04 9:41 ` Martin Storsjö
2022-01-04 13:34 ` J. Dekker
2022-01-05 6:46 ` [FFmpeg-devel] [PATCH v3 1/6] lavc/arm: dont assign hevc_qpel functions for non-multiple of 8 widths Andreas Rheinhardt
2022-01-05 8:30 ` Martin Storsjö [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=69469eb7-e7ce-c839-c5e5-dcd58e45d7a7@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