From: "Martin Storsjö" <martin@martin.st>
To: Andre Kempe <Andre.Kempe@arm.com>
Cc: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] arm64: Add Armv8.3-A PAC support to assembly files
Date: Tue, 22 Feb 2022 15:53:41 +0200 (EET)
Message-ID: <822c688f-f4fa-9b3a-6423-52c983e723bb@martin.st> (raw)
In-Reply-To: <DBBPR08MB55477152C288659E8492A8DFEF339@DBBPR08MB5547.eurprd08.prod.outlook.com>
On Mon, 14 Feb 2022, Andre Kempe wrote:
> This patch adds optional support for Arm Pointer Authentication Codes.
>
> PAC support is turned on or off at compile time using additional
> compiler flags. Unless any of these is enabled explicitly, no additional
> code will be emitted at all.
>
> Signed-off-by: André Kempe <andre.kempe@arm.com>
> ---
> libavcodec/aarch64/fft_neon.S | 3 +-
> libavcodec/aarch64/mdct_neon.S | 17 ++++-
> libavcodec/aarch64/synth_filter_neon.S | 2 +
> libavutil/aarch64/asm.S | 102 +++++++++++++++++++++++--
> 4 files changed, 113 insertions(+), 11 deletions(-)
LGTM, this looks generally correct and consistent to me.
But I realized one thing (which probably should be fixed both here and in
dav1d, but which I guess we can fix separately afterwards too) - I guess
we should only output the .note.gnu.property section if we're targeting
ELF. (I guess that PAC/BTI aren't used on other platforms yet, but it's
plausible that they will be, and then they won't use ELF note sections to
signal 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-02-22 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 12:28 Andre Kempe
2022-02-22 13:53 ` Martin Storsjö [this message]
2022-03-09 13:13 ` 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=822c688f-f4fa-9b3a-6423-52c983e723bb@martin.st \
--to=martin@martin.st \
--cc=Andre.Kempe@arm.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