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ö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] gcc: Don't disable '-ftree-vectorize' on GCC >= 13 on major architectures (PR #20120)
Date: Wed, 6 Aug 2025 10:10:40 +0300 (EEST)
Message-ID: <5b78e216-fea3-632-67c6-11943da50fd@martin.st> (raw)
In-Reply-To: <D4752EAA-213D-49EE-9DF8-4A6436C85BF5@remlab.net>

On Wed, 6 Aug 2025, Rémi Denis-Courmont wrote:

> FWIW I don't really care personally but judging by the original author 
> and their affiliation, the intent was most probably to enable this for 
> RISC-V / RVA23.
>
> On that platform it is *probably* safe to enable vectorisation on all 
> GCC versions but I have not tested it. In fact, I don't have an 
> RVA23-conformant board.

Yeah I was on the fence about including RISC-V among the "modern major 
architectures"; after merging this I'd welcome patches to enable the same 
on more architectures, if the people contributing the patch can at least 
indicate that it working without breaking fate tests for that 
configuration.

// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-08-06  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250805141526.67B6368C25D@ffbox0-bg.ffmpeg.org>
2025-08-06  5:42 ` Rémi Denis-Courmont
2025-08-06  7:10   ` Martin Storsjö [this message]
2025-08-05 14:15 Martin Storsjö

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=5b78e216-fea3-632-67c6-11943da50fd@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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