Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>,
	"Martin Storsjö" <martin@martin.st>
Subject: [FFmpeg-devel] Re: [DISCUSSION] Adding ARM64EC support to FFmpeg
Date: Thu, 23 Oct 2025 00:01:55 +0300 (EEST)
Message-ID: <58b4db0-f02-4871-aa7d-e1a77d6168ec@martin.st> (raw)
In-Reply-To: <6935098.ZFdeClDA30@basile.remlab.net>

On Wed, 22 Oct 2025, Rémi Denis-Courmont via ffmpeg-devel wrote:

> If you want to compile AArch64 FFmpeg for use in emulated x86 processes, 
> then you need a FFmpeg that exposes the same ABI as the x86 FFmpeg. 
> That's going to require a lot of changes throughout the code base (and I 
> doubt people here will agree to them overall).

Can you elaborate on what changes you think would be needed?

The compilers (both MSVC and Clang) in arm64ec mode produce code that is 
ABI compatible with x86_64 code - that's part of the whole point of it. It 
is by default ABI compatible without us doing anything about it.

In arm64ec mode, the compiler defines __x86_64__ (or _M_X64) and does not 
define __aarch64__ (or _M_ARM64). It does define __arm64ec__ (or 
_M_ARM64EC) to distinguish it from regular x86_64 though.


There are a few corner cases though; e.g. the cpuflags exposed by 
av_get_cpu_flags() in an arm64ec build would be arm64 flags, while they 
would be x86_64 flags in an x86_64 build.


As a concrete example, I did fully stock x86_64 and arm64ec builds, with 
both MSVC and mingw tools. I took ffmpeg.exe from the x86_64 build and the 
DLLs from the arm64ec builds, and they ran just fine together. (ffmpeg 
does warn that they are from builds with differing configure lines 
though.) Mixing e.g. an x86_64 avcodec DLL with an arm64ec avutil DLL 
doesn't work though.

// Martin
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-10-22 21:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 10:04 [FFmpeg-devel] " harish.rajaselvan--- via ffmpeg-devel
2025-09-22 11:48 ` [FFmpeg-devel] " Martin Storsjö via ffmpeg-devel
2025-09-23 13:03   ` Harish Raja Selvan via ffmpeg-devel
2025-09-24 12:15     ` Martin Storsjö via ffmpeg-devel
2025-09-30  4:58       ` Harish Raja Selvan via ffmpeg-devel
2025-10-03 12:27         ` Martin Storsjö via ffmpeg-devel
2025-10-22  4:33           ` Harish Raja Selvan via ffmpeg-devel
2025-10-22 11:48             ` Martin Storsjö via ffmpeg-devel
2025-10-23  5:34               ` Harish Raja Selvan via ffmpeg-devel
2025-10-22 17:13             ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-22 21:01               ` Martin Storsjö via ffmpeg-devel [this message]
2025-10-23  6:10                 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-23  6:31                   ` Martin Storsjö via ffmpeg-devel
2025-10-23  7:14                     ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-23  7:15             ` Rémi Denis-Courmont via ffmpeg-devel
2025-09-27  9:00 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-03 12:44   ` Martin Storsjö via ffmpeg-devel
2025-10-03 14:32     ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-03 15:11       ` Martin Storsjö via ffmpeg-devel
2025-10-03 16:39         ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-03 20:49           ` Stephen Hutchinson via ffmpeg-devel
2025-10-04  8:43             ` 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=58b4db0-f02-4871-aa7d-e1a77d6168ec@martin.st \
    --to=ffmpeg-devel@ffmpeg.org \
    --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