Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: "Martin Storsjö" <martin@martin.st>,
	"Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
Cc: "Harish Raja Selvan" <harish.rajaselvan@multicorewareinc.com>,
	"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [GASPP PATCH 1/2] Pass "-machine" options through to armasm
Date: Tue, 20 Jan 2026 16:33:30 +0200
Message-ID: <17AC1F62-DE90-48F9-836F-FC93987ACF00@remlab.net> (raw)
In-Reply-To: <77c5679-f47f-5165-7c5-6d5dd9978cda@martin.st>



Le 20 janvier 2026 15:34:57 GMT+02:00, "Martin Storsjö" <martin@martin.st> a écrit :
>On Tue, 20 Jan 2026, Rémi Denis-Courmont via ffmpeg-devel wrote:
>
>> Do you have a plan to address the outstanding shortcomings? What would the actual performance look like in such case, seen as it would disable most or all of the assembler optimisations?
>
>It is possible to use the current aarch64 assembler as such - even though it does violate the arm64ec ABI.

In other words, "it works except when it doesn't."

You can also mess with X18, TPIDR or SP in a leaf function, as long as you restore them before return. Tests will pass (and even checkasm won't notice). It seems ridiculous that a few GPRs and half the vectors are forbidden, but there are interoperability reasons for this. Windows is riddled with all sorts of weird code doing weird things even to other apps. If it were about calling to/from x86, only the callee-saved GPRs would be justifiably reserved by the ABI.

Given enough users, someone will find a way to unwittingly expose the bug at their expense. The argument was that those 3 apps are hugely popular to begin with: you cannot have the cake and eat it.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2026-01-20 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 12:49 [FFmpeg-devel] " Martin Storsjö via ffmpeg-devel
2025-10-03 12:49 ` [FFmpeg-devel] [GASPP PATCH 2/2] Filter out the cl.exe option -arm64EC from armasm Martin Storsjö via ffmpeg-devel
2025-10-09 12:11 ` [FFmpeg-devel] Re: [GASPP PATCH 1/2] Pass "-machine" options through to armasm Martin Storsjö via ffmpeg-devel
2025-10-10 11:11   ` Harish Raja Selvan via ffmpeg-devel
2025-10-10 13:06     ` Martin Storsjö via ffmpeg-devel
2025-11-07  3:51       ` Harish Raja Selvan via ffmpeg-devel
2025-11-07  8:56         ` Martin Storsjö via ffmpeg-devel
2025-11-17  7:27           ` Harish Raja Selvan via ffmpeg-devel
2026-01-20  7:26             ` Harish Raja Selvan via ffmpeg-devel
2026-01-20 11:32               ` Rémi Denis-Courmont via ffmpeg-devel
2026-01-20 13:34                 ` Martin Storsjö via ffmpeg-devel
2026-01-20 14:33                   ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2026-01-27  7:42                     ` Harish Raja Selvan via ffmpeg-devel
2026-01-27 15:34                       ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-07  9:37         ` Rémi Denis-Courmont via ffmpeg-devel

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=17AC1F62-DE90-48F9-836F-FC93987ACF00@remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=harish.rajaselvan@multicorewareinc.com \
    --cc=martin@martin.st \
    --cc=remi@remlab.net \
    /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