From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 2/3] lavu/riscv: add Zvbb CPU capability detection
Date: Tue, 7 May 2024 22:12:05 +0300
Message-ID: <20240507191208.61372-2-remi@remlab.net> (raw)
In-Reply-To: <20240507191208.61372-1-remi@remlab.net>
This requires Linux kernel version 6.8 or later.
---
libavutil/riscv/cpu.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/libavutil/riscv/cpu.c b/libavutil/riscv/cpu.c
index 69d1afe853..3cf4e25bc9 100644
--- a/libavutil/riscv/cpu.c
+++ b/libavutil/riscv/cpu.c
@@ -54,6 +54,10 @@ int ff_get_cpu_flags_riscv(void)
ret |= AV_CPU_FLAG_RVB_ADDR;
if (pairs[1].value & RISCV_HWPROBE_EXT_ZBB)
ret |= AV_CPU_FLAG_RVB_BASIC;
+#ifdef RISCV_HWPROBE_EXT_ZVBB
+ if (pairs[1].value & RISCV_HWPROBE_EXT_ZVBB)
+ ret |= AV_CPU_FLAG_RV_ZVBB;
+#endif
} else
#endif
#if HAVE_GETAUXVAL
@@ -105,6 +109,9 @@ int ff_get_cpu_flags_riscv(void)
ret |= AV_CPU_FLAG_RVV_F64;
#endif
#endif
+#endif
+#ifdef __riscv_zvbb
+ ret |= AV_CPU_FLAG_RV_ZVBB;
#endif
return ret;
--
2.43.0
_______________________________________________
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:[~2024-05-07 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 19:12 [FFmpeg-devel] [PATCH 1/3] riscv: add Zvbb vector bit manipulation extension Rémi Denis-Courmont
2024-05-07 19:12 ` Rémi Denis-Courmont [this message]
2024-05-07 19:12 ` [FFmpeg-devel] [PATCH 3/3] lavc/ac3dsp: add R-V Zvbb extract_exponents Rémi Denis-Courmont
2024-05-07 20:34 ` [FFmpeg-devel] [PATCH 1/3] riscv: add Zvbb vector bit manipulation extension Martin Storsjö
2024-05-08 6:22 ` Rémi Denis-Courmont
2024-05-08 16:00 [FFmpeg-devel] [PATCHv2 " Rémi Denis-Courmont
2024-05-08 16:00 ` [FFmpeg-devel] [PATCH 2/3] lavu/riscv: add Zvbb CPU capability detection Rémi Denis-Courmont
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=20240507191208.61372-2-remi@remlab.net \
--to=remi@remlab.net \
--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