From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavc/vp9dsp: R-V V ipred dc
Date: Wed, 03 Apr 2024 23:21:54 +0300
Message-ID: <6030011.lOV4Wx5bFT@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+tM=tgpvvt7AhM1+C+xf6xBgQ_X8aJH-=15aA_3j2xJFQ@mail.gmail.com>
Le torstaina 28. maaliskuuta 2024, 4.44.33 EEST flow gg a écrit :
> I don't quite understand, I think here 8x8 because zve64x is not suitable
> for sharing, it shares between dc16x16 and dc32x32, there isn't much common
> code, it would require adding 3 if-else statements and function parameters,
> it feels okay not to extract too.
I agree that we can't realistically share code between the different block
sizes. My point was that the code after getdc is lengthy (after expansion) and
fixed for a given block size, so *that* code could be shared and jumped as
common function tail.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
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-04-03 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 7:42 flow gg
2024-03-02 9:03 ` Rémi Denis-Courmont
2024-03-02 9:48 ` flow gg
2024-03-03 1:59 ` flow gg
2024-03-03 14:46 ` Rémi Denis-Courmont
2024-03-03 15:31 ` flow gg
2024-03-07 11:20 ` flow gg
2024-03-22 6:02 ` flow gg
2024-03-27 15:41 ` Rémi Denis-Courmont
2024-03-28 2:44 ` flow gg
2024-04-03 20:21 ` Rémi Denis-Courmont [this message]
2024-04-07 5:38 ` flow gg
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=6030011.lOV4Wx5bFT@basile.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