On 2014-01-11 18:03:21 +0100, Janne Grunau wrote:
> NEON and VFPv4 are not optional for ARMv8. For cpuflag support we are
> handling both as extensions. This is consistant with x86_64 which
> implies SSE2 which is still handled as extension.
> ---
> configure | 25 ++++++++++--
> libavutil/aarch64/Makefile | 1 +
> libavutil/aarch64/asm.S | 63
> +++++++++++++++++++++++++++++
> libavutil/{cpu_internal.h => aarch64/cpu.c} | 22 ++++------
> libavutil/{cpu_internal.h => aarch64/cpu.h} | 22 +++++-----
> libavutil/cpu.c | 19 +++++++--
> libavutil/cpu.h | 1 +
> libavutil/cpu_internal.h | 1 +
> 8 files changed, 123 insertions(+), 31 deletions(-)
> create mode 100644 libavutil/aarch64/Makefile
> create mode 100644 libavutil/aarch64/asm.S
> copy libavutil/{cpu_internal.h => aarch64/cpu.c} (64%)
> copy libavutil/{cpu_internal.h => aarch64/cpu.h} (57%)
>
> diff --git a/configure b/configure
> index fba8815..58640a4 100755
> --- a/configure
> +++ b/configure
> @@ -1233,6 +1233,15 @@ ARCH_LIST='
> x86_64
> '
>
> +# both NEON and VFPv4 are not really extensions for aarch64 since they are
> +# not optional. They are handled as extensions to support disabling
> +# optimizations via cpu flags. This is consistent with x86_64
> +ARCH_EXT_LIST_AARCH64='
> + neon
> + vfp
> + vfpv4
This is not a good idea since it leads to duplicate entries for neon and
vfp in config.{h,mak}. I'll remove ARCH_EXT_LIST_AARCH64 and add vfp4
for arm
Janne
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
