From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: harish.rajaselvan@multicorewareinc.com,
"Martin Storsjö" <martin@martin.st>,
"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [DISCUSSION] Adding ARM64EC support to FFmpeg
Date: Thu, 23 Oct 2025 10:14:48 +0300
Message-ID: <4A1E91AB-FC60-4B51-9C76-65038D600D7C@remlab.net> (raw)
In-Reply-To: <68c24bcd-716b-fe5-3687-a54fc1346942@martin.st>
Le 23 octobre 2025 09:31:26 GMT+03:00, "Martin Storsjö via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org> a écrit :
>On Thu, 23 Oct 2025, Rémi Denis-Courmont via ffmpeg-devel wrote:
>
>>
>>
>> Le 23 octobre 2025 00:01:55 GMT+03:00, "Martin Storsjö" <martin@martin.st> a écrit :
>>> 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?
>>
>> You're supposed to expose the same binary interface as x86. This is obviously not working correctly for CPU flags, which *are* part of the public libavutil interface, AFAIK.
>
>Yes - although most users of the DLLs won't touch these, so as long as all the libav* DLLs are built in the same form, this won't matter.
I disagree. That's literally a known bug.
And even then, that's only the most obvious issue. It does not seem like anyone has made any serious review/audit of the external interfaces, for things like conditionals, alignment or size mismatches, etc.
If MCW is happy with this kludge, then they can use it on their own. I don't think upstream should merge half-baked stuff though.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-10-23 7:15 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
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 [this message]
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=4A1E91AB-FC60-4B51-9C76-65038D600D7C@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