From: "Martin Storsjö" <martin@martin.st>
To: "Logan.Lyu" <Logan.Lyu@myais.com.cn>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/6] lavc/aarch64: new optimization for 8-bit hevc_pel_bi_pixels
Date: Fri, 1 Dec 2023 21:29:48 +0200 (EET)
Message-ID: <c7c15a0-70ef-3dc2-f358-64985ac7d21@martin.st> (raw)
In-Reply-To: <ebbe7843-26b4-b4eb-51d3-a552d12d1b3@martin.st>
On Fri, 24 Nov 2023, Martin Storsjö wrote:
> Hi Logan,
>
> On Fri, 24 Nov 2023, Logan.Lyu wrote:
>
>> And can you try those .patch files I attached in every email? I
>> downloaded the attachment from the ffmpeg-devel mailing list I subscribed
>> to and applied it, and it seems to work.
>
> Oh, I see - I didn't notice the attached patch. As the patch also was sent
> inline, I only tried to apply the full mail as a patch (which had corrupted
> whitespace somewhere), but the attached patch files did work. Now I've
> successfully applied your patchset, so I can start testing and reviewing it
> when I get time for it. Thanks!
I had a look at the patchset now, it looked mostly good.
I fixed most of the trivial issues I noticed, and pushed with that.
Please have a look at the comments I made, in particular, the weird
+ mov x8, #32
+ str x8, [sp, #-80]!
in patch 5/6 is left untouched as is. Feel free to propose follow-up
patches to fix that. I also didn't try to tweak the scheduling of e.g. the
subs instructions.
// 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".
next prev parent reply other threads:[~2023-12-01 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 2:06 Logan.Lyu
2023-11-19 20:42 ` Michael Niedermayer
2023-11-22 12:30 ` Logan.Lyu
2023-11-22 12:36 ` Martin Storsjö via ffmpeg-devel
2023-11-24 12:19 ` Logan.Lyu
2023-11-24 12:30 ` Martin Storsjö
2023-12-01 19:29 ` Martin Storsjö [this message]
2023-12-01 18:09 ` Martin Storsjö
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=c7c15a0-70ef-3dc2-f358-64985ac7d21@martin.st \
--to=martin@martin.st \
--cc=Logan.Lyu@myais.com.cn \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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