From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Replace br return with ret
Date: Fri, 4 Aug 2023 13:48:51 +0300 (EEST)
Message-ID: <27738246-8171-7c8b-492d-5066d989e5f2@martin.st> (raw)
In-Reply-To: <F3E3CFC9-4F01-45BD-9258-679D52F63D5F@remlab.net>
On Thu, 27 Jul 2023, Rémi Denis-Courmont wrote:
> Hi,
>
> The use of RET vs BR also has microarchitectural side effects. AFAIU, RET should always be paired with an earlier BL/BLR to avoid interfering with branch prediction.
>
> So depending on the circumstances, either one of these should be
> addressed:
> * Clarify that this is actually a function return , and RET should be
> used anyway, regardless of BTI.
This is the case, and the patch looks good to me.
I guess the commit message could be clarified that this is an issue even
without BTI (even if the effect is much harder to notice there).
Would this amended commit message be ok with you? (If no input I guess
I'll push it in a few days.)
---8<---
Subject: aarch64/hevc: Replace br return with ret
This patch changes the return instruction in the tr_32x4 macro from br to
ret.
Function returns should always use the RET instruction instead of BR, to
avoid interfering with branch prediction.
On devices that support BTI, this is observeable as a landing pad is
required when branching with BR. The change fixes
fate-hevc-hdr-vivid-metadata when on hardware with BTI support.
---8<---
// 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-08-04 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 10:26 Casey Smalley
2023-07-27 13:55 ` Rémi Denis-Courmont
2023-07-27 17:22 ` Reimar Döffinger
2023-08-04 9:14 ` Casey Smalley
2023-08-04 10:48 ` Martin Storsjö [this message]
2023-08-08 12:22 Casey Smalley
2023-08-08 17:46 ` 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=27738246-8171-7c8b-492d-5066d989e5f2@martin.st \
--to=martin@martin.st \
--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