This is an automated email from the git hooks/post-receive script. Git pushed a commit to branch master in repository ffmpeg.
commit 087f46674a6e8bcef28a6a6912695ec08e9a70b6 Author: Martin Storsjö <[email protected]> AuthorDate: Tue Dec 16 00:39:51 2025 +0200 Commit: Martin Storsjö <[email protected]> CommitDate: Fri Dec 19 10:01:16 2025 +0000 doc: Document our stance on Windows ARM64EC Explicitly spell it out that we are not going to modify the individual libraries for the purposes of improving conformance to ARM64EC. We may (or may not) accept build system patches for making such a build succeed, provided that it does not require changes to the actual library code. --- doc/platform.texi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/platform.texi b/doc/platform.texi index d9ee436a9f..5ed6997cef 100644 --- a/doc/platform.texi +++ b/doc/platform.texi @@ -330,4 +330,20 @@ and for a build with shared libraries ./configure --target-os=mingw32 --enable-shared --disable-static --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin @end example +@section ARM64EC + +FFmpeg does not intend to support the Windows ARM64EC build configuration; +patches for changing the individual libraries for the purposes of ARM64EC will +not be accepted. + +It may still be possible to build FFmpeg in this build configuration; +such a build may seem to work to some extent. Such a build may have some +amounts of ABI inconsistencies though - which we are not willing to fix. + +(Changing aarch64 assembly code to strictly support ARM64EC would require +ifdeffing/changing essentially all such assembly code, and would be a +huge maintenance burden. Additionally, changing the library ABI +surfaces to fix ABI inconsistencies could require extensive and intrusive +changes.) + @bye _______________________________________________ ffmpeg-cvslog mailing list -- [email protected] To unsubscribe send an email to [email protected]
