Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: Mikhail Nitenko <mnitenko@gmail.com>
Cc: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc/aarch64: h264qpel, add lowpass_8 based functions
Date: Thu, 7 Dec 2023 16:03:36 +0200 (EET)
Message-ID: <cfc952ef-d725-7b3d-6e6a-3938cbd8481@martin.st> (raw)
In-Reply-To: <20231204100035.157285-1-mnitenko@gmail.com>

Hi,

On Mon, 4 Dec 2023, Mikhail Nitenko wrote:

> ---

I think the patch subject is missing to tell that this adds 10 bit 
functions?

> I remodeled the patch (as Martin once suggested), it doesn't
> go to 32bits in lowpass_8_10 and is also using the much
> faster lowpass_8_10_v.
>
> libavcodec/aarch64/h264qpel_init_aarch64.c |  91 +++-
> libavcodec/aarch64/h264qpel_neon.S         | 532 +++++++++++++++++++++
> 2 files changed, 621 insertions(+), 2 deletions(-)

I think the patch overall looks good to me, thanks! I can try to push it a 
bit later.

> diff --git a/libavcodec/aarch64/h264qpel_neon.S b/libavcodec/aarch64/h264qpel_neon.S
> index f4475d96f9..31130a57fd 100644
> --- a/libavcodec/aarch64/h264qpel_neon.S
> +++ b/libavcodec/aarch64/h264qpel_neon.S
> @@ -933,3 +933,535 @@ endfunc
>
>         h264_qpel16     put
>         h264_qpel16     avg
> +
> +//trashes v0-v5
> +.macro  lowpass_8_10    r0,  r1,  r2,  r3,  d0,  d1
> +        ext             v2.16B,     \r0\().16B,  \r1\().16B, #4

This patch uses upper case element specifiers like .16B here; we 
reformatted our assembly to consistenty use lower case element specifiers 
in 184103b3105f02f1189fa0047af4269e027dfbd6 (also see 
7f905f3672da4f1fa28d7cccf1fef7f9984e0480); I can apply this change 
mechanically on this patch before pushing it.

// 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".

  reply	other threads:[~2023-12-07 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 10:00 Mikhail Nitenko
2023-12-07 14:03 ` Martin Storsjö [this message]
2023-12-07 15:10   ` Mikhail Nitenko
2023-12-07 16:21     ` Martin Storsjö
2023-12-07 15:37   ` Mikhail Nitenko

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=cfc952ef-d725-7b3d-6e6a-3938cbd8481@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=mnitenko@gmail.com \
    /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