From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
Subject: Re: [FFmpeg-devel] [PATCH] aarch64: Implement stack spilling in a consistent way.
Date: Tue, 11 Oct 2022 00:29:20 +0300 (EEST)
Message-ID: <614017c8-c8c-e067-b830-3c3599b7b69e@martin.st> (raw)
In-Reply-To: <20221009194714.33606-1-Reimar.Doeffinger@gmx.de>
On Sun, 9 Oct 2022, Reimar.Doeffinger@gmx.de wrote:
> From: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
>
> Currently it is done in several different ways, which
> might cause needless dependencies or in case of
> tx_float_neon.S is incorrect.
>
> Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
> ---
> libavcodec/aarch64/fft_neon.S | 3 +-
> libavcodec/aarch64/h264idct_neon.S | 6 +-
> libavcodec/aarch64/hevcdsp_sao_neon.S | 3 +-
> libavcodec/aarch64/mdct_neon.S | 18 ++----
> libavcodec/aarch64/me_cmp_neon.S | 6 +-
> libavcodec/aarch64/synth_filter_neon.S | 3 +-
> libavcodec/aarch64/vp9itxfm_neon.S | 28 ++++-----
> libavcodec/aarch64/vp9lpf_16bpp_neon.S | 32 +++++------
> libavcodec/aarch64/vp9lpf_neon.S | 80 +++++++++++++-------------
> libavutil/aarch64/tx_float_neon.S | 52 ++++++++---------
> 10 files changed, 109 insertions(+), 122 deletions(-)
This looks reasonable to me, assuming that it passes fate. Do you want to
push it yourself, or do you want me to do 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".
next prev parent reply other threads:[~2022-10-10 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 19:47 Reimar.Doeffinger
2022-10-10 21:29 ` Martin Storsjö [this message]
2022-10-11 7:14 ` Reimar Döffinger
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=614017c8-c8c-e067-b830-3c3599b7b69e@martin.st \
--to=martin@martin.st \
--cc=Reimar.Doeffinger@gmx.de \
--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