Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 4/4] vvcdec: reuse h26x/h2656_deblock_template.c
Date: Tue, 9 Jan 2024 11:05:31 +0800
Message-ID: <CAFXK13cgefzmkwiepPq299sRRM-0LUyBQbBcXn2H+xw_p3OSRg@mail.gmail.com> (raw)
In-Reply-To: <CAEEMt2m_hDAwUuCwkWoGTkzSfkzuL2FX8PKJfTW=k+nMdEzMqw@mail.gmail.com>

On Tue, Jan 9, 2024 at 9:23 AM Ronald S. Bultje <rsbultje@gmail.com> wrote:

> Hi,
>
> On Mon, Jan 8, 2024 at 8:03 PM Nuo Mi <nuomi2021@gmail.com> wrote:
>
> > On Sat, Jan 6, 2024 at 6:52 PM Nuo Mi <nuomi2021@gmail.com> wrote:
> >
> > > ---
> > >  libavcodec/vvc/vvc_filter_template.c | 82 +---------------------------
> > >  1 file changed, 3 insertions(+), 79 deletions(-)
> > >
> > > diff --git a/libavcodec/vvc/vvc_filter_template.c
> > > b/libavcodec/vvc/vvc_filter_template.c
> > > index 9418980c33..671ed7de4e 100644
> > > --- a/libavcodec/vvc/vvc_filter_template.c
> > > +++ b/libavcodec/vvc/vvc_filter_template.c
> > > @@ -461,6 +461,8 @@ static void FUNC(alf_recon_coeff_and_clip)(int16_t
> > > *coeff, int16_t *clip,
> > >  #define FQ2 pix[2  * xstride + 1 * ystride]
> > >  #define FQ3 pix[3  * xstride + 1 * ystride]
> > >
> > > +#include "libavcodec/h26x/h2656_deblock_template.c"
> > >
> > Will merge this in two days if there are no objections to the file and
> > directory names.
> >
>
> Are there options to share the actual generated binary code? The C code
> admittedly is not so important, but it would be great if there was some way
> to ensure that optimizations written for HEVC in some instruction set, work
> for VVC also - or vice versa.
>
Yes. After we merge this, we will send out the mc x86 asm code for review.
It will share the same binary with HEVC.
For SAO/Deblock, we will follow a similar approach, but it needs to be a
little later than mc.
For C code, we can share the binary as well, but it involves some interface
changes, better to do it after all asm is ready.

>
> Ronald
> _______________________________________________
> 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".

  reply	other threads:[~2024-01-09  3:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240103153238.18678-1-nuomi2021@gmail.com>
2024-01-03 15:32 ` [FFmpeg-devel] [PATCH 1/4] hevcdec: move sao template to xvc_sao_template.c Nuo Mi
2024-01-06 10:51   ` [FFmpeg-devel] [PATCH v2 1/4] hevcdec: move sao template to h26x/h2656_sao_template.c Nuo Mi
     [not found]   ` <20240106105132.31509-1-nuomi2021@gmail.com>
2024-01-06 10:51     ` [FFmpeg-devel] [PATCH v2 2/4] vvcdec: reuse h26x/h2656_sao_template.c Nuo Mi
2024-01-06 10:51     ` [FFmpeg-devel] [PATCH v2 3/4] hevcdec: move deblock template to h26x/h2656_deblock_template.c Nuo Mi
2024-01-06 10:51     ` [FFmpeg-devel] [PATCH v2 4/4] vvcdec: reuse h26x/h2656_deblock_template.c Nuo Mi
2024-01-09  1:02       ` Nuo Mi
2024-01-09  1:22         ` Ronald S. Bultje
2024-01-09  3:05           ` Nuo Mi [this message]
2024-01-09 12:50             ` Ronald S. Bultje
2024-01-11 15:05               ` Nuo Mi
2024-01-03 15:32 ` [FFmpeg-devel] [PATCH 2/4] vvcdec: reuse xvc_sao_template.c Nuo Mi
2024-01-03 15:32 ` [FFmpeg-devel] [PATCH 3/4] hevcdec: move deblock template to xvc_deblock_template.c Nuo Mi
2024-01-03 15:32 ` [FFmpeg-devel] [PATCH 4/4] vvcdec: reuse xvc_deblock_template.c 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=CAFXK13cgefzmkwiepPq299sRRM-0LUyBQbBcXn2H+xw_p3OSRg@mail.gmail.com \
    --to=nuomi2021@gmail.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