From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/vvc: Remove NOP condition check in alf_filter_luma
Date: Wed, 17 Jul 2024 00:17:20 +0800
Message-ID: <tencent_A66B9C94E1625A5435C1816034B53EED5709@qq.com> (raw)
In-Reply-To: <tencent_6A1C5A0C35C58034354F3E2D57639C6CE109@qq.com>
> On Jul 17, 2024, at 00:07, Zhao Zhili <quinkblack@foxmail.com> wrote:
>
>
>
>> On Jul 16, 2024, at 20:31, Nuo Mi <nuomi2021@gmail.com> wrote:
>>
>> On Tue, Jul 16, 2024 at 10:50 AM Zhao Zhili <quinkblack@foxmail.com <mailto:quinkblack@foxmail.com>> wrote:
>>
>>> From: Zhao Zhili <zhilizhao@tencent.com <mailto:zhilizhao@tencent.com>>
>>>
>>> If (y + i == vb_above) or (y + i == vb_below), the if body has no
>>> operation.
>>>
>> 👍, How did you find this? From a compiler warning or by reading the code?
>
> There is compiler warning. I found this issue when trying to simplify the logic
> before rewrite in ARM assembly.
Oops, I mean there is “no" compiler warning.
>
>>
>>
>>> ---
>>> libavcodec/vvc/filter_template.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/libavcodec/vvc/filter_template.c
>>> b/libavcodec/vvc/filter_template.c
>>> index 9b3a0e46f7..32777452b7 100644
>>> --- a/libavcodec/vvc/filter_template.c
>>> +++ b/libavcodec/vvc/filter_template.c
>>> @@ -77,7 +77,7 @@ static void FUNC(alf_filter_luma)(uint8_t *_dst,
>>> ptrdiff_t dst_stride, const uin
>>> const int is_near_vb_below = (y + i >= vb_pos) && (y + i
>>> <= vb_pos);
>>> const int is_near_vb = is_near_vb_above ||
>>> is_near_vb_below;
>>>
>>> - if ((y + i < vb_pos) && ((y + i) >= vb_above)) {
>>> + if ((y + i < vb_pos) && ((y + i) > vb_above)) {
>>> p1 = (y + i == vb_pos - 1) ? p0 : p1;
>>> p3 = (y + i >= vb_pos - 2) ? p1 : p3;
>>> p5 = (y + i >= vb_pos - 3) ? p3 : p5;
>>> @@ -85,7 +85,7 @@ static void FUNC(alf_filter_luma)(uint8_t *_dst,
>>> ptrdiff_t dst_stride, const uin
>>> p2 = (y + i == vb_pos - 1) ? p0 : p2;
>>> p4 = (y + i >= vb_pos - 2) ? p2 : p4;
>>> p6 = (y + i >= vb_pos - 3) ? p4 : p6;
>>> - } else if ((y + i >= vb_pos) && ((y + i) <= vb_below)) {
>>> + } else if ((y + i >= vb_pos) && ((y + i) < vb_below)) {
>>> p2 = (y + i == vb_pos ) ? p0 : p2;
>>> p4 = (y + i <= vb_pos + 1) ? p2 : p4;
>>> p6 = (y + i <= vb_pos + 2) ? p4 : p6;
>>> --
>>> 2.42.0
>>>
>>> _______________________________________________
>>> 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".
>>>
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org>
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-devel-request@ffmpeg.org <mailto:ffmpeg-devel-request@ffmpeg.org> with subject "unsubscribe".
>
> _______________________________________________
> 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".
_______________________________________________
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:[~2024-07-16 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 2:49 Zhao Zhili
2024-07-16 12:31 ` Nuo Mi
2024-07-16 16:07 ` Zhao Zhili
2024-07-16 16:17 ` Zhao Zhili [this message]
2024-07-17 13:30 ` Nuo Mi
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=tencent_A66B9C94E1625A5435C1816034B53EED5709@qq.com \
--to=quinkblack@foxmail.com \
--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