diff options
| author | Rémi Denis-Courmont <remi@remlab.net> | 2023-07-14 19:29:32 +0300 |
|---|---|---|
| committer | Rémi Denis-Courmont <remi@remlab.net> | 2023-07-15 22:56:30 +0300 |
| commit | f03223495385f64e11b29b5a51fcef2a93627184 (patch) | |
| tree | cc9c8cbfda5969663e3fef8aae66fc17a6c0882a /libavutil/aarch64 | |
| parent | 82cb4b1c05519523150f589fd020f5df0b66461b (diff) | |
| download | ffmpeg-f03223495385f64e11b29b5a51fcef2a93627184.tar.gz | |
aarch64: remove VFP feature check
This is not actually used for anything. The configure check causes the
CPU feature flag to be set, but nothing consumes it at all.
While AArch64 does have VFP, it is only used for the scalar C code.
Conversely, it is still possible to disable VFP, by changing the
C compiler flags as before (though that only makes sense for an
hypothetical non-standard Armv8 platform without VFP).
Note that this retains the "vfp" option flag, for backward
compatibility and on the very remote but theoretically possible chance
that FFmpeg actually makes use of it in the future.
AV_CPU_FLAG_VFP is retained as it is actually used by AArch32.
Diffstat (limited to 'libavutil/aarch64')
| -rw-r--r-- | libavutil/aarch64/cpu.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/libavutil/aarch64/cpu.c b/libavutil/aarch64/cpu.c index a8cb301dd7..2803b31443 100644 --- a/libavutil/aarch64/cpu.c +++ b/libavutil/aarch64/cpu.c @@ -107,8 +107,7 @@ static int detect_flags(void) int ff_get_cpu_flags_aarch64(void) { int flags = AV_CPU_FLAG_ARMV8 * HAVE_ARMV8 | - AV_CPU_FLAG_NEON * HAVE_NEON | - AV_CPU_FLAG_VFP * HAVE_VFP; + AV_CPU_FLAG_NEON * HAVE_NEON; #ifdef __ARM_FEATURE_DOTPROD flags |= AV_CPU_FLAG_DOTPROD; |