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, 27 Jan 2026 17:34:23 +0200
Message-ID: <61019638.nNK5FJhoec@basile.remlab.net> (raw)
In-Reply-To: <MA5P287MB4625796A7EB8BE3A5C5F1CFC9E90A@MA5P287MB4625.INDP287.PROD.OUTLOOK.COM>
Le tiistaina 27. tammikuuta 2026, 9.42.03 Itä-Euroopan normaaliaika Harish
Raja Selvan via ffmpeg-devel a écrit :
> Hi Martin and Rémi,
>
> Thank you for the detailed explanations.
>
> >From the discussion, we understand that the current situation only covers a
> >small part of what would be required for proper ARM64EC support, and that
> >there are significant remaining gaps.
> We would like to ask one clarification to better understand the direction:
>
> If the remaining technical issues (ABI correctness, ARM64EC-compliant
> assembly, and public interface behavior) were addressed properly, would
> ARM64EC support be something FFmpeg could consider?
It's hard to answer an hypothetical. How would you address those issues?
--
ヅニ-クーモン・レミ
https://www.remlab.net/
_______________________________________________
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:[~2026-01-27 15:35 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
2026-01-27 7:42 ` Harish Raja Selvan via ffmpeg-devel
2026-01-27 15:34 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
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=61019638.nNK5FJhoec@basile.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