From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v5] gcc: Don't disable '-ftree-vectorize' if gcc version higher than 13. Date: Fri, 11 Jul 2025 23:41:28 +0200 Message-ID: <20250711214128.GU29660@pb2> (raw) In-Reply-To: <7634ba8e-7e76-a11b-98f-d7d5cb61eb1@martin.st> [-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --] Hi Martin On Thu, Jul 10, 2025 at 02:35:10PM +0300, Martin Storsjö wrote: > On Thu, 10 Jul 2025, Jiawei wrote: > > > Hi Martin, > > > > Is there any progress for this patch, should I resend it to the mailing > > list again? > > When I posted the updated version of the patch, the patchwork test runners > noticed that this patch causes test failures on Loongarch. So modern > versions of GCC still do have vectorization bugs, at least on some > architectures. > > I'm unsure if we should allow it everywhere, and just single out loongarch > as a case where it is known broken, or if we should only let GCC enable it > on the major architectures that we've tested. I think for architectures where there is an active maintainer, that maintainer should decide. For architectures where there is noone looking after them, its safer to leave it disabled. Otherwsie users could be having complex to debug issues to deal with and noone in ffmpeg able to replicate thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB He who knows, does not speak. He who speaks, does not know. -- Lao Tsu [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
next prev parent reply other threads:[~2025-07-11 21:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250613083704.6858-1-jiawei@iscas.ac.cn> 2025-06-13 8:42 ` Martin Storsjö 2025-06-14 22:49 ` Michael Niedermayer 2025-06-16 7:37 ` Martin Storsjö [not found] ` <a37b238c-c136-4a13-96ba-0bca77fdcb38@iscas.ac.cn> [not found] ` <ec574b73-bf1d-4174-9e8f-617101a5820c@iscas.ac.cn> 2025-07-10 11:35 ` Martin Storsjö [not found] ` <871c0cb0-5433-43db-a57c-aee96bdeae16@iscas.ac.cn> 2025-07-10 12:44 ` Martin Storsjö 2025-07-11 21:41 ` Michael Niedermayer [this message] 2025-06-17 22:17 ` compn
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=20250711214128.GU29660@pb2 \ --to=michael@niedermayer.cc \ --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