summaryrefslogtreecommitdiff
path: root/libavutil/cpu_internal.h
diff options
context:
space:
mode:
authorRĂ©mi Denis-Courmont <remi@remlab.net>2022-09-26 17:52:21 +0300
committerLynne <dev@lynne.ee>2022-09-27 13:19:52 +0200
commitb95e2fbd85e93b58d019ad0e3da64a72ee7cc3d5 (patch)
treeccf3b030be7df33cf5312936bb017469a3522e68 /libavutil/cpu_internal.h
parent179830108dbeb1c6b73105ae2234cf04874728b4 (diff)
downloadffmpeg-b95e2fbd85e93b58d019ad0e3da64a72ee7cc3d5.tar.gz
lavu/cpu: detect RISC-V base extensions
This introduces compile-time and run-time CPU detection on RISC-V. In practice, I doubt that FFmpeg will ever see a RISC-V CPU without all of I, F and D extensions, and if it does, it probably won't have run-time detection. So the flags are essentially always set. But as things stand, checkasm wants them that way. Compare the ARMV8 flag on AArch64. We are nowhere near running short on CPU flag bits.
Diffstat (limited to 'libavutil/cpu_internal.h')
-rw-r--r--libavutil/cpu_internal.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/libavutil/cpu_internal.h b/libavutil/cpu_internal.h
index 650d47fc96..634f28bac4 100644
--- a/libavutil/cpu_internal.h
+++ b/libavutil/cpu_internal.h
@@ -48,6 +48,7 @@ int ff_get_cpu_flags_mips(void);
int ff_get_cpu_flags_aarch64(void);
int ff_get_cpu_flags_arm(void);
int ff_get_cpu_flags_ppc(void);
+int ff_get_cpu_flags_riscv(void);
int ff_get_cpu_flags_x86(void);
int ff_get_cpu_flags_loongarch(void);