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: Harish Raja Selvan <harish.rajaselvan@multicorewareinc.com>
Cc: "harish.rajaselvan--- via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>,
	"Martin Storsjö" <martin@martin.st>
Subject: [FFmpeg-devel] Re: [DISCUSSION] Adding ARM64EC support to FFmpeg
Date: Wed, 24 Sep 2025 15:15:12 +0300 (EEST)
Message-ID: <582fec83-771a-eef4-d5d1-6ff5621cff98@martin.st> (raw)
In-Reply-To: <MA5P287MB46255A20D768B0629777A25B9E1DA@MA5P287MB4625.INDP287.PROD.OUTLOOK.COM>

On Tue, 23 Sep 2025, Harish Raja Selvan wrote:

> Following up on the discussion above on ARM64EC support, I’ve prepared a
> patch to
> update gas-preprocessor.pl that enables FFmpeg to be compiled for ARM64EC
> target on Windows. This change ensures that -m flags are not eliminated for
> ARM64EC target, allowing assembly files to preprocess as expected. This
> avoids build failures.

It is entirely unclear to me what -m flags you would expect to be seeing 
here. I can understand the part of the patch to filter out the flag 
-arm64EC, but I don't see where a flag "ARM64EC" would come from for 
preprocess_c_cd, or where any -m flags would come from.

To make sense of the patch, I would suggest you at least explain what kind 
of configure flags you are using in combination with these patches.

My attempts with ARM64EC with MSVC are configured with --arch=arm64 
--target-os=win32 --toolchain=msvc --extra-cflags="-arm64EC" 
--extra-ldflags="-machine:arm64ec". I guess you are doing something other 
than that, if you're getting -m flags somewhere.

Ideally, post both your build system patches and the gas-preprocessor 
patch at the same time.

Also, don't top post.

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

  reply	other threads:[~2025-09-24 12:15 UTC|newest]

Thread overview: 13+ 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 [this message]
2025-09-30  4:58       ` Harish Raja Selvan via ffmpeg-devel
2025-10-03 12:27         ` Martin Storsjö 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=582fec83-771a-eef4-d5d1-6ff5621cff98@martin.st \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=harish.rajaselvan@multicorewareinc.com \
    --cc=martin@martin.st \
    /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 http://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/ http://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