From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] avutil/x86/x86inc: make AVX imply CLMUL (PR #21733)
Date: Wed, 11 Feb 2026 16:10:35 -0000
Message-ID: <177082623593.25.6269708989176266974@009cbcb3d8cd> (raw)
PR #21733 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21733
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21733.patch
The clmul instructions are present in all AVX CPUs (Sandy Bridge and newer, Bulldozer and newer).
>From e4cb580bcb809e8120a3bebdb8ce29164f905f3d Mon Sep 17 00:00:00 2001
From: James Almer <jamrial@gmail.com>
Date: Wed, 11 Feb 2026 13:09:19 -0300
Subject: [PATCH] avutil/x86/x86inc: make AVX imply CLMUL
The clmul instructions are present in all AVX CPUs (Sandy Bridge and newer,
Bulldozer and newer).
Signed-off-by: James Almer <jamrial@gmail.com>
---
libavutil/x86/x86inc.asm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavutil/x86/x86inc.asm b/libavutil/x86/x86inc.asm
index 0e80ebed43..8983eab4b7 100644
--- a/libavutil/x86/x86inc.asm
+++ b/libavutil/x86/x86inc.asm
@@ -955,8 +955,8 @@ BRANCH_INSTR jz, je, jnz, jne, jl, jle, jnl, jnle, jg, jge, jng, jnge, ja, jae,
%assign cpuflags_sse42 (1<<11) | cpuflags_sse4
%assign cpuflags_aesni (1<<12) | cpuflags_sse42
%assign cpuflags_clmul (1<<13) | cpuflags_sse42
-%assign cpuflags_gfni (1<<14) | cpuflags_aesni|cpuflags_clmul
-%assign cpuflags_avx (1<<15) | cpuflags_sse42
+%assign cpuflags_gfni (1<<14) | cpuflags_aesni
+%assign cpuflags_avx (1<<15) | cpuflags_clmul
%assign cpuflags_xop (1<<16) | cpuflags_avx
%assign cpuflags_fma4 (1<<17) | cpuflags_avx
%assign cpuflags_fma3 (1<<18) | cpuflags_avx
--
2.52.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-02-11 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=177082623593.25.6269708989176266974@009cbcb3d8cd \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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